Native crash on OS X while trying to reproduce memory leak.
swpalmer at gmail.com
Tue Oct 23 12:20:37 PDT 2012
On 2012-10-23, at 3:12 PM, Mike Swingler <swingler at apple.com> wrote:
> 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.
The standard OS X crash reporter window opened and I submitted the report. Doesn't that mean that it will get in the queue to be reviewed by Apple? (Perhaps after a few duplicate stack traces or something?)
More information about the openjfx-dev