Native crash on OS X while trying to reproduce memory leak.
swingler at apple.com
Tue Oct 23 12:12:14 PDT 2012
On Oct 23, 2012, at 12:05 PM, Scott Palmer <swpalmer at gmail.com> wrote:
> On 2012-10-23, at 1:26 PM, Scott Kovatch <scott.kovatch at oracle.com> wrote:
>> On Oct 21, 2012, at 3:49 PM, Scott Palmer <swpalmer at gmail.com> wrote:
>> The crashed thread:
>>> Thread 28 Crashed:: CVDisplayLink
>>> 0 libsystem_kernel.dylib 0x00007fff8f68a212 __pthread_kill + 10
>> All of that, except for the signal handling code, is Apple code. It's probably going to be hard to know if we fed it garbage or a bug in the GL driver.
> What I expected. Perhaps the crash report will eventually trickle down to somebody at Apple that can do something more.
Not if the JVM is catching it. HotSpot should actually not catch crashes that are on threads that are not attached to the JVM.
>> Another thing I noticed, but probably not related to this specific problem:
>>> 0x11c299000 - 0x11c2a2ff7 com.apple.java.JavaRuntimeSupport (14.5.0 - 14.5.0) <A08E8799-F5FF-3CBB-A753-FC2AF260ABEB> /System/Library/Frameworks/JavaVM.framework/Frameworks/JavaRuntimeSupport.framework/JavaRuntimeSupport
>>> 0x11c2b1000 - 0x11c2bbfff JavaNativeFoundation (1) <F1FE02AF-1A2C-3EF7-9D1A-312FA21B51B9> /System/Library/Frameworks/JavaVM.framework/Versions/A/Frameworks/JavaNativeFoundation.framework/Versions/A/JavaNativeFoundation
>>> 0x11c2c6000 - 0x11c2cbfff com.apple.JavaVM (14.5.0 - 14.5.0) <83C8C2AB-E99D-39FF-80B4-90A7DEB1DAFB> /System/Library/Frameworks/JavaVM.framework/Versions/A/JavaVM
>>> 0x11c2d3000 - 0x11c2d8fff JavaLaunching (1) <B1E18D32-6FF1-3882-B25A-558A2FB18B55> /System/Library/PrivateFrameworks/JavaLaunching.framework/Versions/A/JavaLaunching
>> How are you getting this code to load?
> It is a NetBeans 7.2 Swing + JavaFX project that was run from the IDE.
>> Is this a bundled application?
> No. But I haven't looked into the magic that the NB Ant script is doing for Swing + JavaFX it even makes a main class derived from Applet for some reason.. I didn't bother to sanitize it.
>> I would only expect to see this code with Apple's application stub. It could be that JavaVM.framework is pulling it in -- JavaNativeFoundation and JavaRuntimeSupport rely on it.
>> Just curious….
> Now you've got me curious too.
This is normal. The AWT and Aqua LaF in Java 7 links against JavaNativeFoundation and JavaRuntimeSupport to do it's business.
More information about the openjfx-dev