The developers are aware of the issue. I'm not 100% sure but if I am correctly remembering what Johan K said, that particular fault lies in an externally developed library and is thus rather hard for them to work with.
It is likely the developers of that library are aware of the problem and working to fix it themselves, but I don't have any info on that at all, not even half-remembered info.
