Comment 1 for bug 2057899

@bjornt and I had a call about this issue and came to the conclusion that we won't be able to improve anything in version 3.5. But the problem still exists and should be fixed in future versions.