Fix for issue #4946.