You are welcome! I understand your feelings completely, I struggled myself with this bug for a very long time.

It’s such a pity that it remains unfixed for years. :( One of the worst attitudes towards users ever.

I just came across your article. All I can say is thank you and god bless your soul. You ended my two-year misery with this nasty bug.

Thank you.

Another resource, added as a comment on your article, to feed the search engines, to help others in the future.

A very interesting technical account, which is right on topic for this bug:

Serious Java bug triggered by X-Setup tweak
http://www.x-setup.net/forum/showthread.php?p=6856

It also provides a tool for triggering the problem on demand.

Now it’s over to Java Engineering. :-)

Best regards,

Doesn’t surprise me it was previously reported. Almost year since I wrote this post and who knows how long back issue spans.

Evaluation on that entry says my blog was unavailable (see recent posts, got hacked hard) so you might want to comment there that this post is online again.

FYI -

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6877831

Even if the bug-report is declared a dupe, the FAQ for the Java SE JRE needs to be patched. :-)

Particularly for domestic end-users of the JRE, there’s not a lot of connect-the-dots pages out there, to grep onto.

Best regards,

Brian

Yeah, this is probably most obscure bug I had ever had to deal with. :)

Java is considerd big thing for business aplications, cross-platform, etc… But personally I prefer native and portable apps over frameworks. You don’t get to run software in drastically different environments without performance overhead and compatibility issues.

This is the most technical insight I have read, to date. :-)

I have also encountered this appalling bug:

http://forums.java.net/jive/thread.jspa?messageID=344456

“Detuning” ClearType might force what is a heisenbug into a bohrbug. Otherwise the GDI++ (cited above) reliably crashes Java and so is a good tool for examining the problem.

Given the crashes are so uninformative, who knows how many have suffered, or are suffering.

Someone with the technical nous, should knock on the door of Java Engineering, firmly, resolutely but politely, and get them to fix this, as well as a FAQ entry.

Mission Critical != Java, at the moment.

Best regards,

Brian

You are welcome. :) It’s indeed extremely nasty bug and with very obscure reason.

This page was read over hundred times already (guess we aren’t only unlucky enough) and I hope it was of help in each case.

Olaf