Re: RFR [9] 8031050: [macosx] Crash while awt starting

2014-02-03 Thread David Holmes
On 3/02/2014 11:54 PM, Alan Bateman wrote: On 03/02/2014 13:18, Chris Hegarty wrote: Hi, An old issue has resurfaced because of a change in AWT. AWT, now, on Mac OS X, attaches a system graphics thread to the running VM, using JNI_AttachCurrentThread. This change can result in a NPE, if a secur

Re: RFR [9] 8031050: [macosx] Crash while awt starting

2014-02-03 Thread Mandy Chung
On 2/3/2014 5:18 AM, Chris Hegarty wrote: Hi, An old issue has resurfaced because of a change in AWT. AWT, now, on Mac OS X, attaches a system graphics thread to the running VM, using JNI_AttachCurrentThread. This change can result in a NPE, if a security manager is installed, and the securi

Re: RFR [9] 8031050: [macosx] Crash while awt starting

2014-02-03 Thread Alan Bateman
On 03/02/2014 13:18, Chris Hegarty wrote: Hi, An old issue has resurfaced because of a change in AWT. AWT, now, on Mac OS X, attaches a system graphics thread to the running VM, using JNI_AttachCurrentThread. This change can result in a NPE, if a security manager is installed, and the securit

RFR [9] 8031050: [macosx] Crash while awt starting

2014-02-03 Thread Chris Hegarty
Hi, An old issue has resurfaced because of a change in AWT. AWT, now, on Mac OS X, attaches a system graphics thread to the running VM, using JNI_AttachCurrentThread. This change can result in a NPE, if a security manager is installed, and the security manager tries to print the name of the c