Yeah, the direct cause of the horrible native application crash was fixed for other platforms (see my post here, which I assume is the one you are thinking of), but fixing that is somewhat tangential to truly addressing the problem... That fix just changes it from a crash in a native library to a null-pointer exception in Java code, which is an oh-so-fractionally cleaner way for it to crash. Unless I'm misunderstanding it, all of these shenanigans are due to the JRE demanding hardware acceleration and not getting it when running in a VM, which is a problem they'll need to specifically tackle anew and is specific to the Mac OS platform. It might even have been an explicit design choice to require hardware acceleration, in which case we're up the proverbial creek...
Cheers,
--
Darius