Issue with running Java applets on Safari 6.1
I conducted a system capability check on the course site I access (Defense Acquisition University) and one of the results indicated that I do not have the capability to run applets (requirements to run all courses). I verified my setings and I do have Java ver. 7 update 45 installed. I verified Safari's security preferences and confirmed that the "Enable Java Script" is checked. I tried configuring the website settings for Java plug-in but cannot figure out how to add url on the configured websites box. Is there any way to enable running applets in Safari? Any help is appreciated. Thanks in advance.
Please post a link to the page you're having trouble with (unless it requires a password.)
Similar Messages
-
Security Issues with Javascript, Java Applet interaction
First the main idea of the project. I have a system where I need to use an applet to process an image and display it on a web page.
I have written the applet that does the image processing and it saves the finished image on the users disc. It then uses the showDocument(url) method to pass the URL of the local file to a java script function on the html page.
This is where the problem occurs. Firefox won't display that image and complains about a security error because the remote page is linking to a local file. Interestingly enough IE6 on windows has no issue displaying the generated image.
I really have two questions.
1)Is there a quick/dirty fix that just simply gets around the security barrier Firefox has?
2)Is there some other, more elegant, way of getting an image from an applet to the webpage. It doesn't matter if it requires writing to disc or not.
Thanks! Any suggestions out there will help me.First the main idea of the project. I have a system where I need to use an applet to process an image and display it on a web page.
I have written the applet that does the image processing and it saves the finished image on the users disc. It then uses the showDocument(url) method to pass the URL of the local file to a java script function on the html page.
This is where the problem occurs. Firefox won't display that image and complains about a security error because the remote page is linking to a local file. Interestingly enough IE6 on windows has no issue displaying the generated image.
I really have two questions.
1)Is there a quick/dirty fix that just simply gets around the security barrier Firefox has?
2)Is there some other, more elegant, way of getting an image from an applet to the webpage. It doesn't matter if it requires writing to disc or not.
Thanks! Any suggestions out there will help me. -
I am having trouble with my JAVA Applet. It isn't functioning on SAFARI. It seems to have stopped working and I used it on SAFARI last year. Any suggestions?
Post in the Safari forum area.
-
I'm trying to run a Java applet with safari, but everytime I go to the webpage all I get is a grey box with a picture of a coffee cup that has two arrows circling it. Nothing loads after that. Any idea how to fix this?
Hi ad1054,
Are you sure you have java 1.6 and if so, how did you get it? I believe the latest version available from apple is 1.5.0_06. Java 1.6 was only just released by Sun, and, if I'm not mistaken, only for PC and Linux. Apple may be waiting to force people to pay for Leopard to get Java 1.6. (Though you can get a beta version from developer.apple.com.) As Hawaiian_Starman mentioned above, you can check your java version.
That said, you don't have to worry about lower versions of Java because Java is backwards compatible. In fact, if you use Firefox (sorry, but I just checked it in Safari, and got a blank page so I guess Safari, like IE, doesn't support this) and go to "about:plugins" you will see something like
<pre>
Java Embedding Plugin 0.9.5g2
File name: MRJPlugin.plugin
Runs Java applets using the latest installed versions of Java. For more information: Java Embedding Plugin. Run version test: Test Your JVM.
MIME Type Description Suffixes Enabled
application/x-java-vm Embedded JVM xjv Yes
application/x-java-applet Embedded Java Applet xja Yes
application/x-java-applet;version=1.1 Embedded Java Applet xja11 Yes
application/x-java-applet;version=1.1.1 Embedded Java Applet xja111 Yes
application/x-java-applet;version=1.1.2 Embedded Java Applet xja112 Yes
application/x-java-applet;version=1.1.3 Embedded Java Applet xja113 Yes
application/x-java-applet;version=1.2 Embedded Java Applet xja12 Yes
application/x-java-applet;version=1.2.1 Embedded Java Applet xja121 Yes
application/x-java-applet;version=1.2.2 Embedded Java Applet xja122 Yes
application/x-java-applet;version=1.3 Embedded Java Applet xja13 Yes
application/x-java-applet;version=1.3.1 Embedded Java Applet xja131 Yes
application/x-java-applet;version=1.4 Embedded Java Applet xja14 Yes
application/x-java-applet;version=1.4.1 Embedded Java Applet xja141 Yes
application/x-java-applet;version=1.4.2 Embedded Java Applet xja142 Yes
application/x-java-applet;version=1.5 Embedded Java Applet xja15 Yes
</pre>
You can see from this list that all versions up to and including the currently installed one are supported. The only thing you have to fear is that the applet you are trying to use was compiled with Java 1.6 and is not itself backwards compatible. However, when I made a test applet of this type, I got a red X, and no coffee cup.
If you see the red X, and I think the coffee cup as well, you should be able to right-click (or ctrl-click) the icon. If so, this will give you a menu with "console" and "about" choices. "About" will give you the version of Java you have, and "console" is supposed to show you the errors that kept the applet from working. (However, with my Java 1.6 test, the console was empty.)
I hope this helps.
1.5GB, 2.16 GHz Core Duo, 15.4" Macbook Pro Mac OS X (10.4.8) -
Problems running java applet in 1.4.2
Hi,
I need some help with running an applet in the following environment:
Win 98 ver 2
jre 1.4.2
IE 6.0
My applet runs in AOL within the same environment. However, the one we wrote does not run in this at all. I get the characteristic grey patch. Additionally, even the 1.4.2 test applets do not run in my environment. I get status messages like "load:class LoadUpload_100 not found".
I need to mention that 1.2 applets run in the same environment without any issues.
Any help on this will be greatly appreciate.
Thanks,
Akoul.
[email protected]If you use Swing, you will need to convert your HTML using Sun's HTML converter.
-
Crashes when running Java Applets and trying to open Security System Preferences
Browser crashes when trying to run Java Applets, I've tried 4 different browsers. This is the crash report.
Process: java [90472]
Path: /usr/bin/java
Identifier: com.apple.javajdk16.cmd
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: Google Chrome Helper EH [90460]
Date/Time: 2012-02-17 15:04:44.693 -0500
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report: 9110 sec
Crashes Since Last Report: 8
Per-App Interval Since Last Report: 43908 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: DFA20D26-FD7E-4507-AAA9-EBF29199EC56
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread: 31 Java: Thread-11
Application Specific Information:
Java information:
Exception type: Bus Error (0xa) at pc=00000000
Java VM: Java HotSpot(TM) 64-Bit Server VM (20.4-b02-402 mixed mode macosx-amd64)
Current thread (102a13000): JavaThread "Thread-11" daemon [_thread_in_Java, id=607662080, stack(124283000,124383000)]
Stack: [124283000,124383000]
Java Threads: ( => current thread )
126525000 JavaThread "Thread-26" daemon [_thread_blocked, id=878407680, stack(1344b7000,1345b7000)]
126524000 JavaThread "Thread-25" daemon [_thread_in_native, id=877346816, stack(1343b4000,1344b4000)]
102f20800 JavaThread "Thread-21" daemon [_thread_blocked, id=636690432, stack(125e32000,125f32000)]
102b96000 JavaThread "Thread-20" daemon [_thread_in_native, id=550666240, stack(120ca8000,120d28000)]
102b95000 JavaThread "Thread-19" daemon [_thread_blocked, id=632483840, stack(125a2f000,125b2f000)]
1261e6000 JavaThread "Java Sound Event Dispatcher" daemon [_thread_blocked, id=591368192, stack(1232f9000,1233f9000)]
10191b800 JavaThread "Thread-15" daemon [_thread_blocked, id=611905536, stack(12468f000,12478f000)]
1029c7800 JavaThread "Thread-14" daemon [_thread_blocked, id=610844672, stack(12458c000,12468c000)]
102b11000 JavaThread "Thread-13" daemon [_thread_blocked, id=609783808, stack(124489000,124589000)]
101929000 JavaThread "Thread-12" daemon [_thread_blocked, id=608722944, stack(124386000,124486000)]
=>102a13000 JavaThread "Thread-11" daemon [_thread_in_Java, id=607662080, stack(124283000,124383000)]
1029d2000 JavaThread "Poller SunPKCS11-Darwin" daemon [_thread_blocked, id=541855744, stack(1203c1000,1204c1000)]
101a43800 JavaThread "thread applet-Rs2Applet.class-1" [_thread_blocked, id=534294528, stack(11fc8b000,11fd8b000)]
102a07800 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=527765504, stack(11f651000,11f751000)]
102878000 JavaThread "JVM[id=0]-Heartbeat" daemon [_thread_blocked, id=490639360, stack(11d2e9000,11d3e9000)]
101943000 JavaThread "AWT-EventQueue-2" [_thread_blocked, id=494882816, stack(11d6f5000,11d7f5000)]
102933000 JavaThread "Applet 1 LiveConnect Worker Thread" [_thread_blocked, id=466014208, stack(11bb6d000,11bc6d000)]
101933800 JavaThread "Browser Side Object Cleanup Thread" [_thread_blocked, id=191471616, stack(10b59a000,10b69a000)]
101944000 JavaThread "AWT-EventQueue-0" [_thread_blocked, id=493821952, stack(11d5f2000,11d6f2000)]
1029ae800 JavaThread "CacheCleanUpThread" daemon [_thread_blocked, id=492761088, stack(11d4ef000,11d5ef000)]
102a04800 JavaThread "CacheMemoryCleanUpThread" daemon [_thread_blocked, id=491700224, stack(11d3ec000,11d4ec000)]
102b2e000 JavaThread "SysExecutionTheadCreator" daemon [_thread_blocked, id=489578496, stack(11d1e6000,11d2e6000)]
1018e6800 JavaThread "Java Plug-In Pipe Worker Thread (Client-Side)" daemon [_thread_in_native, id=464945152, stack(11ba68000,11bb68000)]
101a46800 JavaThread "AWT-Shutdown" [_thread_blocked, id=463884288, stack(11b965000,11ba65000)]
101934800 JavaThread "AWT-AppKit" daemon [_thread_in_native, id=1896107200, stack(7fff5f400000,7fff5fc00000)]
101933000 JavaThread "Timer-0" [_thread_blocked, id=190410752, stack(10b497000,10b597000)]
1018cd000 JavaThread "traceMsgQueueThread" daemon [_thread_blocked, id=188145664, stack(10b26e000,10b36e000)]
102853000 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=172019712, stack(10a30d000,10a40d000)]
102852800 JavaThread "C2 CompilerThread1" daemon [_thread_blocked, id=170958848, stack(10a20a000,10a30a000)]
102851800 JavaThread "C2 CompilerThread0" daemon [_thread_blocked, id=169897984, stack(10a107000,10a207000)]
102851000 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=168837120, stack(10a004000,10a104000)]
102850000 JavaThread "Surrogate Locker Thread (Concurrent GC)" daemon [_thread_blocked, id=167776256, stack(109f01000,10a001000)]
102842800 JavaThread "Finalizer" daemon [_thread_blocked, id=162287616, stack(1099c5000,109ac5000)]
102841800 JavaThread "Reference Handler" daemon [_thread_blocked, id=161226752, stack(1098c2000,1099c2000)]
101801000 JavaThread "main" [_thread_blocked, id=5246976, stack(100401000,100501000)]
Other Threads:
10283d000 VMThread [stack: 1097bf000,1098bf000] [id=160165888]
10285d000 WatcherThread [stack: 10a410000,10a510000] [id=173080576]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
par new generation total 19136K, used 9943K [7eae00000, 7ec2c0000, 7ece00000)
eden space 17024K, 46% used [7eae00000, 7eb5a5ec8, 7ebea0000)
from space 2112K, 100% used [7ec0b0000, 7ec2c0000, 7ec2c0000)
to space 2112K, 0% used [7ebea0000, 7ebea0000, 7ec0b0000)
concurrent mark-sweep generation total 144152K, used 110056K [7ece00000, 7f5ac6000, 7fae00000)
concurrent-mark-sweep perm gen total 62268K, used 37524K [7fae00000, 7feacf000, 800000000)
Code Cache [103801000, 104192000, 106801000)
total_blobs=2217 nmethods=1445 adapters=734 free_code_cache=40529280 largest_free_block=47360
Virtual Machine Arguments:
JVM Args: -D__jvm_launched=1329508711033330 -Xbootclasspath/a:/System/Library/Frameworks/JavaVM.framework/Resources/Deploy. bundle/Contents/Resources/Java/deploy.jar:/System/Library/Frameworks/JavaVM.fram ework/Resources/Deploy.bundle/Contents/Resources/Java/javaws.jar:/System/Library /Frameworks/JavaVM.framework/Resources/Deploy.bundle/Contents/Resources/Java/plu gin.jar -Djava.applet.host=world8.runescape.com -Dapple.awt.UIElement=true -Dsun.awt.warmup=true -Xmx256m -Xss1m -Xincgc -XX:+UseConcMarkSweepGC -Dsun.java2d.noddraw=true
Java Command: sun.plugin2.main.client.PluginMain write_pipe_name=/var/folders/Aa/Aa4dzX7xHJmbzy55DpvyiE+++TI/-Tmp-/.java.deploy. 90460.994108354874315847
Launcher Type: SUN_STANDARD
Physical Memory: Page Size = 4k, Total = 3840M, Free = 774M
Thread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 com.apple.CoreFoundation 0x00007fff864f2902 __CFRunLoopRun + 1698
3 com.apple.CoreFoundation 0x00007fff864f1d8f CFRunLoopRunSpecific + 575
4 com.apple.HIToolbox 0x00007fff857827ee RunCurrentEventLoopInMode + 333
5 com.apple.HIToolbox 0x00007fff857825f3 ReceiveNextEventCommon + 310
6 com.apple.HIToolbox 0x00007fff857824ac BlockUntilNextEventMatchingListInMode + 59
7 com.apple.AppKit 0x00007fff85ae6eb2 _DPSNextEvent + 708
8 com.apple.AppKit 0x00007fff85ae6801 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
9 libawt.jnilib 0x000000010b6f1f0d -[NSApplicationAWT nextEventMatchingMask:untilDate:inMode:dequeue:] + 124
10 com.apple.AppKit 0x00007fff85aac68f -[NSApplication run] + 395
11 libawt.jnilib 0x000000010b69e19c +[AWTStarter startAWT:] + 1495
12 libawt.jnilib 0x000000010b69db16 -[CPerformer perform] + 93
13 com.apple.Foundation 0x00007fff8357745f __NSThreadPerformPerform + 219
14 com.apple.CoreFoundation 0x00007fff864f43d1 __CFRunLoopDoSources0 + 1361
15 com.apple.CoreFoundation 0x00007fff864f25c9 __CFRunLoopRun + 873
16 com.apple.CoreFoundation 0x00007fff864f1d8f CFRunLoopRunSpecific + 575
17 java 0x000000010000483f 0x100000000 + 18495
18 java 0x0000000100004296 0x100000000 + 17046
19 java 0x0000000100001a94 0x100000000 + 6804
Thread 1:
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x00000001038069b3 0 + 4353714611
11 ??? 0x00000001038069b3 0 + 4353714611
12 ??? 0x000000010380685a 0 + 4353714266
13 ??? 0x000000010380685a 0 + 4353714266
14 ??? 0x0000000103801438 0 + 4353692728
15 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
16 libclient64.dylib 0x00000001010a4f16 JVM_Lseek + 192613
17 libclient64.dylib 0x00000001010c8e0e JVM_FindLoadedClass + 3186
18 libclient64.dylib 0x00000001010c8cb6 JVM_FindLoadedClass + 2842
19 java 0x0000000100002cef 0x100000000 + 11503
20 java 0x000000010000323c 0x100000000 + 12860
21 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
22 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 2: Java: Exception Handler Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libSystem.B.dylib 0x00007fff8864aa17 mach_msg_server + 468
3 libclient64.dylib 0x000000010100e7cb jio_snprintf + 41425
4 libclient64.dylib 0x000000010100e683 jio_snprintf + 41097
5 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
6 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 3: Java: Gang worker#0 (Parallel GC Threads)
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d1a3 jio_snprintf + 35753
7 libclient64.dylib 0x0000000101025fa4 jio_vsnprintf + 312
8 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
9 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
10 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 4: Java: Gang worker#1 (Parallel GC Threads)
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d1a3 jio_snprintf + 35753
7 libclient64.dylib 0x0000000101025fa4 jio_vsnprintf + 312
8 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
9 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
10 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 5: Java: Concurrent Mark-Sweep GC Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d1a3 jio_snprintf + 35753
7 libclient64.dylib 0x0000000101302097 JVM_Timeout + 883428
8 libclient64.dylib 0x000000010122803c JVM_Yield + 40397
9 libclient64.dylib 0x000000010122783d JVM_Yield + 38350
10 libclient64.dylib 0x00000001012277af JVM_Yield + 38208
11 libclient64.dylib 0x000000010122764e JVM_Yield + 37855
12 libclient64.dylib 0x00000001012273eb JVM_Yield + 37244
13 libclient64.dylib 0x000000010121edca JVM_Yield + 2907
14 libclient64.dylib 0x000000010102c3dc jio_vsnprintf + 25968
15 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
16 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
17 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 6: Java: VM Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d995 jio_snprintf + 37787
3 libclient64.dylib 0x000000010102c54a jio_vsnprintf + 26334
4 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
5 libclient64.dylib 0x000000010100d1a3 jio_snprintf + 35753
6 libclient64.dylib 0x00000001010a3f8f JVM_Lseek + 188638
7 libclient64.dylib 0x00000001010a3cdf JVM_Lseek + 187950
8 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
9 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
10 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 7: Java: Reference Handler
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103a3d848 0 + 4356036680
9 ??? 0x00000001039622d4 0 + 4355138260
10 ??? 0x0000000103801438 0 + 4353692728
11 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
12 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
13 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
14 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
15 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
16 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
17 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
18 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
19 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 8: Java: Finalizer
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103a3d848 0 + 4356036680
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x00000001038069b3 0 + 4353714611
11 ??? 0x00000001038069b3 0 + 4353714611
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 9: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x00007fff885e6c0a kevent + 10
1 libSystem.B.dylib 0x00007fff885e8add _dispatch_mgr_invoke + 154
2 libSystem.B.dylib 0x00007fff885e87b4 _dispatch_queue_invoke + 185
3 libSystem.B.dylib 0x00007fff885e82de _dispatch_worker_thread2 + 252
4 libSystem.B.dylib 0x00007fff885e7c08 _pthread_wqthread + 353
5 libSystem.B.dylib 0x00007fff885e7aa5 start_wqthread + 13
Thread 10: Java: Surrogate Locker Thread (Concurrent GC)
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d10a jio_snprintf + 35600
7 libclient64.dylib 0x00000001010c2261 JVM_IsPrimitiveClass + 6521
8 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
9 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
10 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
11 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
12 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 11: Java: Signal Dispatcher
0 libSystem.B.dylib 0x00007fff885cddb6 semaphore_wait_trap + 10
1 libclient64.dylib 0x00000001010c2aa3 JVM_IsPrimitiveClass + 8635
2 libclient64.dylib 0x00000001010c252a JVM_IsPrimitiveClass + 7234
3 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
4 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
5 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
6 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 12: Java: C2 CompilerThread0
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d10a jio_snprintf + 35600
7 libclient64.dylib 0x00000001010c9319 JVM_Write + 346
8 libclient64.dylib 0x00000001010c3913 JVM_IsPrimitiveClass + 12331
9 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
10 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
11 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
12 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
13 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 13: Java: C2 CompilerThread1
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d10a jio_snprintf + 35600
7 libclient64.dylib 0x00000001010c9319 JVM_Write + 346
8 libclient64.dylib 0x00000001010c3913 JVM_IsPrimitiveClass + 12331
9 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
10 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
11 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
12 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
13 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 14: Java: Low Memory Detector
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d1a3 jio_snprintf + 35753
7 libclient64.dylib 0x00000001010c5318 JVM_IsPrimitiveClass + 18992
8 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
9 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
10 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
11 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
12 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 15: Java: VM Periodic Task Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d995 jio_snprintf + 37787
3 libclient64.dylib 0x00000001011afc26 JVM_GetClassInterfaces + 11348
4 libclient64.dylib 0x00000001010c73a7 JVM_IsPrimitiveClass + 27327
5 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
6 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 16: Java: traceMsgQueueThread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x0000000103806d34 0 + 4353715508
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 17: Java: Timer-0
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x000000010380685a 0 + 4353714266
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 18: Java: AWT-Shutdown
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x0000000103806d34 0 + 4353715508
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 19: Java: Java Plug-In Pipe Worker Thread (Client-Side)
0 libSystem.B.dylib 0x00007fff885d8466 read + 10
1 libdeploy.jnilib 0x0000000109d4d5d9 Java_com_sun_deploy_net_socket_UnixSocketImpl_unStreamSocketRead + 140
2 ??? 0x0000000103811d6e 0 + 4353760622
3 ??? 0x000000010380696e 0 + 4353714542
4 ??? 0x000000010380696e 0 + 4353714542
5 ??? 0x000000010380696e 0 + 4353714542
6 ??? 0x000000010380696e 0 + 4353714542
7 ??? 0x000000010386d2b4 0 + 4354134708
8 ??? 0xfda21644ff67b8d7 0 + 18276194723421468887
Thread 20: Java: SysExecutionTheadCreator
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x0000000103801438 0 + 4353692728
12 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
13 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
14 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
15 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
16 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
17 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
18 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
19 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
20 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 21: Java: CacheMemoryCleanUpThread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x00000001038069b3 0 + 4353714611
11 ??? 0x00000001038069b3 0 + 4353714611
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 22: Java: CacheCleanUpThread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x0000000103801438 0 + 4353692728
12 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
13 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
14 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
15 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
16 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
17 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
18 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
19 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
20 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 23: Java: AWT-EventQueue-0
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103a3d848 0 + 4356036680
9 ??? 0x0000000103aaac60 0 + 4356484192
Thread 24: Java: Browser Side Object Cleanup Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x00000001038069b3 0 + 4353714611
11 ??? 0x00000001038069b3 0 + 4353714611
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 25: Java: Applet 1 LiveConnect Worker Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x0000000103806d34 0 + 4353715508
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 26: Java: AWT-EventQueue-2
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103a3d848 0 + 4356036680
9 ??? 0x0000000103aaac60 0 + 4356484192
Thread 27: Java: JVM[id=0]-Heartbeat
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d995 jio_snprintf + 37787
3 libclient64.dylib 0x000000010102c54a jio_vsnprintf + 26334
4 libclient64.dylib 0x00000001010b25a1 JVM_MonitorWait + 4011
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103a3d848 0 + 4356036680
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x00000001038069b3 0 + 4353714611
11 ??? 0x00000001038069b3 0 + 4353714611
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 28: Java: Java2D Disposer
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_mDid you get this fixed? I have had this error everytime I try to access my bank, inventory, and ither things. Please help.
-
Run Java Applet (JAR) in Visual Basic
Hi,
I want to start a java applet within a visual basic form.
One opportunity would be to implement a browser control and load a html file with the applet object in it.
Is there a way to load the applet in VB without a browser control?
Thanks for any tips & hintsOh, I'm aware of this way to start the applet.
That's not what I want to achieve.
I want to have the possiblity to integtrate my applet in a vb application (in a window in the vb app). For example if I would use MDI Forms I want the java applet to start as a child within the main vb window.
I thought of using a browser OCX Control and loading a html which has the object tag with the java applet.
Thanks anyway! -
HT3131 Are there any ventilation issues with running a macbook air in clamshell mode?
Are there any ventilation issues with running a macbook air in clamshell mode?
...that makes sense to me.
but, why do so many MBA users (on this forum and others) claim that ventilation occurs through the keyboard? Is this claim based on an old macbook design?
for example, here's a related discussion (although fairly old):
11-08-2010, 12:16 PM
#6 (permalink)
SP Forsythe
Notebook Evangelist
Join Date: Jul 2007
Location: California
Posts: 660
Rep Power: 14
Re: Is it safe to use MBP with screen lid closed? Leave charge on always?
Quote:
Originally Posted by tHE j0KER
Actually I you shouldn't close the lid while running on an external screen. The keyboard of the Macbook is an air intake for the fan. Close the lid, and it could overheat.
A common misconception of unknown origin. The intake and the exhaust for the cooling fan on the 13" MB and MBP are both located on the rear slot at the base of the hinge. In fact, you can actually see the divider that separates the intake flow from the output flow. If it were through the keyboard crevices, then an awful lot of overheats would result from people using impermeable keyboard covers, as well as Apple's warranty department would be flipping out over the Apple store carrying such covers. iSkin ProTouch FX Keyboard Cover for all MacBooks - Black Printed Keys on White - Apple Store (U.S.)
Does one think that Apple sells these only for use when the Notebook is off??? http://store.apple.com/us/product/TW...co=MTM3OTUwMDE Closing the lid, whilst operating the unit actually results in cooler operation due to reduction in power consumed by operating the display, which in supporting the on-board display generates heat far greater than simply powering the video port..
Does one think that Apple sells these for use only when the MacBook is off? http://store.apple.com/us/product/TW...co=MTM3OTUwMDEApples direction for use is specifically for when using with an external display.
Currently using:
Apple MacBook Air 13" mid 2011 1.8GHz Core i7 4GB 256 GB SSD Lion & Ubuntu Linux via Fusion
MacBook Air 11.6" late 2010 1.6 GHZ, 320M, 4GB 180 GB SSD Upgraded OWC), OS X Lion
11-08-2010, 02:34 PM
#7 (permalink)
ajreynol
Notebook Virtuoso
Join Date: Mar 2009
Location: Ann Arbor, MI
Posts: 2,542
Rep Power: 18
Re: Is it safe to use MBP with screen lid closed? Leave charge on always?
once again, I've tried a few of these keyboard covers. the Moshi keyboard cover is the ONLY one I can recommend. the others are too thick or change the keyboard experience too much.
17" Apple MacBook Pro | i7 2720m | 160GB SSD + 750GB | 16GB | HD 6750M 1GB
Dell 435MT | i7 920 | 10GB RAM | 7.64TB HDDs | HD 6970 | Win7+SL
HP Elitebook 2710p Tablet PC | 1.8GHz C2D | 4GB RAM | 160GB HDD | X3100
Apple iPhone 4 32GB | Apple iPad 64GB (Gen 3)
Stop random laptop wakeup | 5K500.B bench data | How to Disable PowerMiser
Disable Vaio beep when pressing volume or special keys
11-08-2010, 03:34 PM
#8 (permalink)
doh123
Without ME its just AWESO
Join Date: Feb 2009
Posts: 3,282
Rep Power: 22
Re: Is it safe to use MBP with screen lid closed? Leave charge on always?
1. Closing the cover will cause more heat. This is not because of covering the keyboard very much (though it does help some heat be retained). It's mainly because of the shape of the hinge and the fact when closed it covers up the back vent a lot more. For the best cooling, it is best to have the screen open. Just run it as a dual monitor, but make the external the Primary monitor, and if you don't want to use the built in, just turn its backlight off and don't use it.
2. The thing you plug into the wall is not a battery charger. The actual "charger" is built into the computer. It knows when to charge and when not to. If the little light on the power plug is amber, then its charging your battery. When its green, its just powering the laptop and NOT charging your battery at all.
Mac OS X Gamer/Porter
(We do exist!)
Wineskin 2.5 is available!. Turn Windows apps into Mac apps for free!
11-08-2010, 03:38 PM
#9 (permalink)
Wolfpup
Notebook Virtuoso
Join Date: Jun 2007
Posts: 3,871
Rep Power: 28
Re: Is it safe to use MBP with screen lid closed? Leave charge on always?
I'd leave the lid open, at least partially...yes it may be fine not doing that, but you are making heat dissipate worse, of course could even theoretically hurt the screen.
As for the battery...well there's really only two choices, have it plugged in or not. As others mentioned, you can't overcharge the battery. It can be damaged a bit from heat, but of course the number one thing that's going to damage it is discharging it...so it's a no brainer-use it plugged in whenever possible, and try to charge it whenever possible when it's not plugged in.
11-08-2010, 03:45 PM
#10 (permalink)
SP Forsythe
Notebook Evangelist
Join Date: Jul 2007
Location: California
Posts: 660
Rep Power: 14
Re: Is it safe to use MBP with screen lid closed? Leave charge on always?
Quote:
Originally Posted by doh123
1. Closing the cover will cause more heat. This is not because of covering the keyboard very much (though it does help some heat be retained). It's mainly because of the shape of the hinge and the fact when closed it covers up the back vent a lot more. For the best cooling, it is best to have the screen open. Just run it as a dual monitor, but make the external the Primary monitor, and if you don't want to use the built in, just turn its backlight off and don't use it.
Nope. Apple would disagree with you on that one. Any "closure", which is, when compared to the amount of CFM, is insignificant. In fact, the opening size remains the same. it is only deflected at a slight angle when the lid is closed. Tilt your MBP and see. As well, shutting down the display lowers the heat being generated, even in the lower case. As I said, if it were a problem, Apple would not be selling stands designed to operate your unit in the closed position as the original poster of this thread proposes to do.
Currently using:
Apple MacBook Air 13" mid 2011 1.8GHz Core i7 4GB 256 GB SSD Lion & Ubuntu Linux via Fusion
MacBook Air 11.6" late 2010 1.6 GHZ, 320M, 4GB 180 GB SSD Upgraded OWC), OS X Lion -
Can anyone help with the java applet issue
Hello everyone,
This is my first thread in this forum,
I need a little help with the form developer...
I have oracle 9i db , 9i form developer
I don't want to run the form i created as a java applet
HOW IS THAT DONE i.e NOT IN THE INTERNET EXPLORER?????????
***IF ITS POSSIBLEHello,
I don't want to run the form i created as a java applet
No chance, because the Web Forms client is an applet and cannot be anything else.
Francois -
Problem running Java applets since Java update 2 (1.6.0_20)
Hi,
Since I upgraded to Java update 2, Java applets started having problems. The most noticeable ones are:
Non-modal windows appear behing the browser Window (tested Safari 4, 5, Chrome 5).
Double buffering not working as usual (slower, white boxes appear when dragging a window, etc.)
Slower rendering in general
The same applications run perfectly using Java Web Start. And they used to work very well also in Java update 1.
The application can be tested here (press ok if a login prompt appears):
Java applet: http://jmap3.k2geospatial.com/montreal_applet/
Java Web Start: http://jmap3.k2geospatial.com/montreal_jws/dockingClient.jnlp
Our applications running in applets use the new plug-in 2 with JNLP files.
Notice the Java startup splash (the animated sun-like logo) is not moving as smoothly as usual. It is very jerky now.
Are these problems known by anyone?
How can I downgrade Java to previous version?
sorry I cross-posted this in Unix forum also. I think it is better here.
Thank you,
Jean-Robert
K2 GeospatialSince the last Java update on mac, all my OpenGL applets stop working and now just shows a white screen on Chrome, Firefox and Opera. They was working well on all browsers (Safari/WebKit,Chrome,Firefox,Opera) just before the update.
The trouble maker seem to be the java plugin 2 and the new offscreen rendering pipeline, as reported by jrhaddad with the disucssion linked to the different Java/OpenGL community forums.
This is a huge regression for me, and I think for all hobbies/ independent developers and all companies who are doing some Java/OpenGL develoment. All our work just stop working since this update.
If would really want to know from Apple if they are working on this problem and/or how this can be solved.
Should this be fixed by Apple with a new java update, or should the various browsers must upgrade their applet support plugins according to the new java plugin 2 changes ?
Best Regards,
Jérôme -
Database connection with a Java applet
I am having trouble figuring out what I am doing wrong.
I am able to connect to the remote database from inside JDeveloper 9.0.3 and execute some simple SQL statements.
The problem is when I try to run this applet on a web page to test it I get some exceptions.
with e.message()
access denied (java.util.PropertyPermission oracle.jserver.version read)
java.security.AccessControlException: access denied (java.util.PropertyPermission oracle.jserver.version read)
I know from within the IDE I assume the security settings are lax or non-exsistant.
any ideas?
Thanks,
MartinJava applets can only access their host machine. If your database is located on a different server than the web server then you get these errors. To access a database located on a different machine you can use the so callled Applet - Servlet tunelling. You actually use a servelt as a proxy. The applet calls the servlet and the servlet accesses the database.
There is a lot of info on these issues in java.sun.com.
hope this helps! -
Can't load Java applets in Safari
Ever since I installed Snow Leopard, Safari can't load Java applets. I get a blue Lego brick with a question mark, and a message telling me that Java was not found.
Firefox is unaffected, and I get the same error whether Safari is open in 32-bit or 64-bit mode. Programs written in Java, such as Vuze, are unaffected.Create another admin user account log into it, and see if the problem persists. If not, the issue's within the original account, usually amongst preference (plist) files. If so, then it's system-wide and reinstalling the 10.6.2 COMBO update, repairing permissions, and restarting should do the trick.
-
"Cancelled Opening the Page" when trying to run Java applet?
Hello just a quick question (I didn't know where else to ask) - I downloaded the Safari beta for Windows to try it out. So far so good, but one of the main sites I go to is a Java applet chat - I can load other applets just fine but for some reason this site keeps the gray cup Java icon and the status bar says "Cancelled opening the page". I've tried loading it as a tab, and as the only active window and the same thing happens; I'm unable to load the site. It works fine in other browsers - is this some issue with the beta?
Thank you all for your time and your help...everything is working great now :o)
Hope you all have a great day. -
Cannot load java applets in Safari
I have several accounts on my machine. In one, the one I use most of the time, Safari will not load java applets. I have checked preferences and compared with those set on the other accounts. They are the same, including enabling javva and javascript. I have removed the Safari plist. I have repaired permissions. I have reset safari, cleared history and caches, used Cocktail to clear caches. I have rebooted.
I set up a new test account and it works fine.
What's going on, and how do I cure it?I will try the pram reset, though I am not confident of it since this problem affects only one account.
On the new account business. I note that when I set up a new account, before I launch safari, there are no files in the Library related to Safari. They are created on the first launch. If I delete them all, then they are recreated on another launch. What if, in the affected user directory, I exported the bookmarks and/or dragged the bookmarks file to the desktop. Then deleted all evidence of safari from the account. I should now have, in effect, a virgin install of safari. Launching it would create all of the necessary files and directories. If safari works with java applets, or does not, I can simply move the bookmarks back in and be no worse off than I was in the beginning.
Any serious fault with that? I am working at home today so cannot do this until I am in the office on Monday. -
BROWSER HANGING WITH LOADING JAVA APPLET
HI
WHEN I RUN THE FORM ON THE EXTERNAL
BROWSER.(USING OPTION RUN A FORM ON THE WEB).
FILLING IN ALL THE DETAILS.
BROWSER HANGS WITH MESSAGE LOADING JAVA APPLET.
TEST.FMX IS IN THE FORMS60 PATH.
I NEED HELP THANKS
DEEPAK.
nullTry using the java console to get more info on what is hapenning.
If you have using Jinitator its on the jinitator control panel.
Maybe you are looking for
-
Error in writing to directory /tmp/OraInstall2009-09-18_09-03-18AM. Please
Hi all, oracle Unbrekable linux 32 bit oracle 10.2.0.1 i got this error while installing oracle universal installer [vishal@localhost database]$ ./runInstaller Starting Oracle Universal Installer... Checking installer requirements... Checking operati
-
If I purchase lightroom but want to install on both a pc and a mac is that possible from just a download version rather than ordering a disc?
-
Hi Experts, How to generate a PDF form using the Interactive Form UI in WebDynpro JAVA ? Regards, Krishna Balaji T
-
Setting in sideshow in Apple TV
Hi Why can I not change the settings in sideshow photos in Apple TV. Like take ramdom off and show all my photos stright through one after the other plus I can't change defalt music. Ta
-
Camera Raw updates Date Taken in JPG Files
Hi, I have CS6/CR 7.2. I have had this issue where my file dates became changed (8000 odd files) so I had to restore 23000 files from backup . When investigating trying to find out what happened. when I open a JPG from Windows Explorer, photoshop