Duplicate :
|
|
Duplicate :
|
|
Relates :
|
The bug is probably a regression of the following fix: JDK-8043869 Reproducible with SwingSet2 started from the command line. The following warning is printed to the console: NSScreen should be called the first time from the main thread (usually as part of -[NSApplication init]) to maintain consistency. ( 0 AppKit 0x00007fff84c1609a +[NSScreen _prepare] + 56 1 libobjc.A.dylib 0x00007fff8f2e0bd0 _class_initialize + 655 2 libobjc.A.dylib 0x00007fff8f2ef3c9 lookUpImpOrForward + 172 3 libobjc.A.dylib 0x00007fff8f2db1ac objc_msgSend + 236 4 libsplashscreen.dylib 0x0000000120cd0e1c SplashNSScreen + 44 5 libsplashscreen.dylib 0x0000000120ccf8af SplashGetScaledImageName + 95 6 java 0x00000001029a89b3 ShowSplashScreen + 76 7 java 0x00000001029aa810 PostJVMInit + 263 8 java 0x00000001029a7b26 JavaMain + 2455 9 libsystem_pthread.dylib 0x00007fff81f1e780 _pthread_body + 131 10 libsystem_pthread.dylib 0x00007fff81f1e6fd _pthread_body + 0 11 libsystem_pthread.dylib 0x00007fff81f1c94d thread_start + 13 The issue is reproducible on 10.10 Yosemite
|