Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
minimwatch hangs after update
27-02-2014, 22:59
Post: #1
minimwatch hangs after update
Hi,


each time when minimwatch notifies me that updates are available and I agree to install these updates minimwatch tries to restart itself. The icon in menu disappears and I am not able to start minimwatch again the normal way (klicking the icon). Only after killing the still running mw processes I am able to start minimwatch again. The updates are installing properly. This behavior is the same since the automatic update feature was introduced.

I am wondering if this is a common problem because this behavior is the same on both of my two macs. But I havn't found others having the same problem..

This is OSX 10.9.1
java version "1.7.0_51"

axelk@plumplori ~$ ps xau | grep -i minim
axelk 355 6,0 1,3 5108352 105748 ?? S 10:18pm 0:05.43 /Applications/MinimWatch.app/Contents/MacOS/../Resources/oracle/MinimWatch/Contents/MacOS/JavaAppLauncher
axelk 367 0,0 0,0 2432780 492 s000 R+ 10:19pm 0:00.00 grep -i minim
axelk 349 0,0 0,0 2441628 1012 ?? S 10:18pm 0:00.01 /bin/sh /Applications/MinimWatch.app/Contents/MacOS/MinimAppLauncher
axelk@plumplori ~$ kill 349
axelk@plumplori ~$ kill 355



Axel
Find all posts by this user
Quote this message in a reply
27-02-2014, 23:13
Post: #2
RE: minimwatch hangs after update
(27-02-2014 22:59)axelk Wrote:  Hi,


each time when minimwatch notifies me that updates are available and I agree to install these updates minimwatch tries to restart itself. The icon in menu disappears and I am not able to start minimwatch again the normal way (klicking the icon). Only after killing the still running mw processes I am able to start minimwatch again. The updates are installing properly. This behavior is the same since the automatic update feature was introduced.

I am wondering if this is a common problem because this behavior is the same on both of my two macs. But I havn't found others having the same problem..

This is OSX 10.9.1
java version "1.7.0_51"

axelk@plumplori ~$ ps xau | grep -i minim
axelk 355 6,0 1,3 5108352 105748 ?? S 10:18pm 0:05.43 /Applications/MinimWatch.app/Contents/MacOS/../Resources/oracle/MinimWatch/Contents/MacOS/JavaAppLauncher
axelk 367 0,0 0,0 2432780 492 s000 R+ 10:19pm 0:00.00 grep -i minim
axelk 349 0,0 0,0 2441628 1012 ?? S 10:18pm 0:00.01 /bin/sh /Applications/MinimWatch.app/Contents/MacOS/MinimAppLauncher
axelk@plumplori ~$ kill 349
axelk@plumplori ~$ kill 355



Axel

Is this problem caused by an update to MinimWatch or an update to MinimServer? There haven't been any updates to MinimWatch since update 16 was released on 10th February.

MinimServer update 21 was released yesterday. Did you see this problem after getting a prompt to install update 21 today?
Find all posts by this user
Quote this message in a reply
27-02-2014, 23:21
Post: #3
RE: minimwatch hangs after update
(27-02-2014 23:13)simoncn Wrote:  
(27-02-2014 22:59)axelk Wrote:  Hi,


each time when minimwatch notifies me that updates are available and I agree to install these updates minimwatch tries to restart itself. The icon in menu disappears and I am not able to start minimwatch again the normal way (klicking the icon). Only after killing the still running mw processes I am able to start minimwatch again. The updates are installing properly. This behavior is the same since the automatic update feature was introduced.

I am wondering if this is a common problem because this behavior is the same on both of my two macs. But I havn't found others having the same problem..

This is OSX 10.9.1
java version "1.7.0_51"

axelk@plumplori ~$ ps xau | grep -i minim
axelk 355 6,0 1,3 5108352 105748 ?? S 10:18pm 0:05.43 /Applications/MinimWatch.app/Contents/MacOS/../Resources/oracle/MinimWatch/Contents/MacOS/JavaAppLauncher
axelk 367 0,0 0,0 2432780 492 s000 R+ 10:19pm 0:00.00 grep -i minim
axelk 349 0,0 0,0 2441628 1012 ?? S 10:18pm 0:00.01 /bin/sh /Applications/MinimWatch.app/Contents/MacOS/MinimAppLauncher
axelk@plumplori ~$ kill 349
axelk@plumplori ~$ kill 355



Axel

Is this problem caused by an update to MinimWatch or an update to MinimServer? There haven't been any updates to MinimWatch since update 16 was released on 10th February.

MinimServer update 21 was released yesterday. Did you see this problem after getting a prompt to install update 21 today?

Yes. It was yesterdays server update which inspired me to write my post here :) But I think this happens each time when updates are available.. no matter if server / streaming plugin or minimwatch updates after klicking through the ok buttons the 'note' icon disappears in the osx menubar.
Find all posts by this user
Quote this message in a reply
28-02-2014, 00:10
Post: #4
RE: minimwatch hangs after update
(27-02-2014 23:21)axelk Wrote:  Yes. It was yesterdays server update which inspired me to write my post here Smile But I think this happens each time when updates are available.. no matter if server / streaming plugin or minimwatch updates after klicking through the ok buttons the 'note' icon disappears in the osx menubar.

Did the server relaunch automatically after doing the update? You can tell whether this happened by seeing whether the server icon is present after you have manually restarted MinimWatch.

Does the minim icon disappear completely or does it change to a "grey" state indicating no server is available?

Can you make the problem happen by doing a manual server update from the Packages tab in the Properties dialog? For example, if you manually replace update 21 by update 20 by typing minimserver-0.8-update-20 in the 'Other package' field and clicking Install, followed by clicking Relaunch after the install has completed, do you see the same problem?

Is it possible that some other program on the Mac is interfering with MinimWatch? See this post for an example of this kind of problem.
Find all posts by this user
Quote this message in a reply
28-02-2014, 00:37
Post: #5
RE: minimwatch hangs after update
(28-02-2014 00:10)simoncn Wrote:  Did the server relaunch automatically after doing the update? You can tell whether this happened by seeing whether the server icon is present after you have manually restarted MinimWatch.
the server relaunched automatically but I am not sure what you mean by 'server icon' .. the 'note' icon I think is from minimwatch. It disappeared completely.

Quote:Does the minim icon disappear completely or does it change to a "grey" state indicating no server is available?
disappeared completely.

Quote:Can you make the problem happen by doing a manual server update from the Packages tab in the Properties dialog? For example, if you manually replace update 21 by update 20 by typing minimserver-0.8-update-20 in the 'Other package' field and clicking Install, followed by clicking Relaunch after the install has completed, do you see the same problem?
doing a manual 'update' to 20 as you instructed works fine. Server restarts. Icon turns to yellow, then to normal (no bg colour).
But then the notification for the 21 update shows up and after doing the update to 21 I am running in the original problem. No icon. have to kill these two processes to be able to start minimwatch again.

Quote:Is it possible that some other program on the Mac is interfering with MinimWatch? See this post for an example of this kind of problem.
Possible.
I will have a closer look. At least I am now able to trigger the problem :) .. but not today, need to go to bed.
Thanks !

Axel
Find all posts by this user
Quote this message in a reply
28-02-2014, 12:37
Post: #6
RE: minimwatch hangs after update
(28-02-2014 00:37)axelk Wrote:  the server relaunched automatically but I am not sure what you mean by 'server icon' .. the 'note' icon I think is from minimwatch. It disappeared completely.

If any servers are running, MinimWatch displays a "minim note" icon for each server. This is what I meant by "server icon". If no server is running, MinimWatch displays a single grey "minim note" icon to show that there is no server.

Quote:doing a manual 'update' to 20 as you instructed works fine. Server restarts. Icon turns to yellow, then to normal (no bg colour).
But then the notification for the 21 update shows up and after doing the update to 21 I am running in the original problem. No icon. have to kill these two processes to be able to start minimwatch again.

This is very helpful for narrowing down the problem. It sounds like there might be a deadlock or hang in MinimWatch after the "Relaunch now" message prompt has been closed. Please do the following:

1) Use ps -ef to find the PID of the MinimWatch Java process (JavaAppLauncher, not MinimAppLauncher)

2) Enter the command "jstack <pid>" where <pid> is the PID from step 1

3) Copy and paste the output from jstack here.

Many thanks!
Find all posts by this user
Quote this message in a reply
28-02-2014, 13:39
Post: #7
RE: minimwatch hangs after update
Hello Simon,

here is the jstack of the hanging JavaAppLauncher.



axelk@plumplori ~$ ps -ef | grep -i minim
501 334 170 0 12:19am ?? 0:00.01 /bin/sh /Applications/MinimWatch.app/Contents/MacOS/MinimAppLauncher
501 342 334 0 12:19am ?? 0:24.44 /Applications/MinimWatch.app/Contents/MacOS/../Resources/oracle/MinimWatch/Contents/MacOS/JavaAppLauncher
501 566 249 0 1:32pm ttys000 0:00.00 grep -i minim
axelk@plumplori ~$ jstack 342
2014-02-28 13:33:01
Full thread dump Java HotSpot™ 64-Bit Server VM (24.51-b03 mixed mode):

"Attach Listener" daemon prio=5 tid=0x00007f9c92842800 nid=0x13753 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-57" daemon prio=5 tid=0x00007f9c92925000 nid=0xe90b runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-56" daemon prio=5 tid=0x00007f9c941f0800 nid=0xe607 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-55" daemon prio=5 tid=0x00007f9c938cf000 nid=0xec07 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-54" daemon prio=5 tid=0x00007f9c92945000 nid=0xe413 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"TimerQueue" daemon prio=5 tid=0x00007f9c91955800 nid=0x10b07 waiting on condition [0x000000011e669000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000007d7b181b0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Abst​ractQueuedSynchronizer.java:2043)
at java.util.concurrent.DelayQueue.take(DelayQueue.java:209)
at javax.swing.TimerQueue.run(TimerQueue.java:171)
at java.lang.Thread.run(Thread.java:744)

"Thread-39" daemon prio=5 tid=0x00007f9c92805000 nid=0xe717 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-38" daemon prio=5 tid=0x00007f9c92837800 nid=0xd703 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-37" daemon prio=5 tid=0x00007f9c9407f000 nid=0xf507 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-36" daemon prio=5 tid=0x00007f9c9207b800 nid=0xbb0b runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-35" daemon prio=5 tid=0x00007f9c92852000 nid=0xea07 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-31" daemon prio=5 tid=0x00007f9c91805000 nid=0xcc03 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-30" daemon prio=5 tid=0x00007f9c93951800 nid=0xe003 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-29" daemon prio=5 tid=0x00007f9c9408f000 nid=0xdf03 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-28" daemon prio=5 tid=0x00007f9c94095800 nid=0xde03 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-27" daemon prio=5 tid=0x00007f9c91881000 nid=0xd603 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-23" daemon prio=5 tid=0x00007f9c94080000 nid=0xd503 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-20" daemon prio=5 tid=0x00007f9c93925000 nid=0xd203 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-18" daemon prio=5 tid=0x00007f9c918e0000 nid=0xdd03 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-17" daemon prio=5 tid=0x00007f9c94873800 nid=0xd103 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-16" daemon prio=5 tid=0x00007f9c9282c800 nid=0xd003 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-15" daemon prio=5 tid=0x00007f9c940af000 nid=0xcf03 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-14" daemon prio=5 tid=0x00007f9c91903000 nid=0xe203 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-13" daemon prio=5 tid=0x00007f9c9484b000 nid=0xd403 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Thread-6" prio=5 tid=0x00007f9c9406a000 nid=0xc903 in Object.wait() [0x00000001213f2000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000007d7b280d0> (a org.jminim.lib.OhNetService$TimerThread)
at org.jminim.lib.OhNetService$TimerThread.run(OhNetService.java:844)
- locked <0x00000007d7b280d0> (a org.jminim.lib.OhNetService$TimerThread)

"Thread-5" prio=5 tid=0x00007f9c9389a000 nid=0xc703 in Object.wait() [0x00000001212ef000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:503)
at org.jminim.lib.OhNetService$ActionThread.run(OhNetService.java:799)
- locked <0x00000007d7b206e8> (a org.jminim.lib.OhNetService$ActionThread)

"Thread-3" prio=5 tid=0x00007f9c9183e800 nid=0xc503 in Object.wait() [0x00000001211ec000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at org.jminim.core.RuntimeImpl$TimerThread.run(RuntimeImpl.java:2463)
- locked <0x00000007d7b30000> (a org.jminim.core.RuntimeImpl$TimerThread)

"Thread-2" prio=5 tid=0x00007f9c94865000 nid=0xc303 in Object.wait() [0x00000001210e9000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000007d7b28140> (a org.jminim.core.RuntimeImpl$ActionThread)
at java.lang.Object.wait(Object.java:503)
at org.jminim.core.RuntimeImpl$ActionThread.run(RuntimeImpl.java:2417)
- locked <0x00000007d7b28140> (a org.jminim.core.RuntimeImpl$ActionThread)

"Thread-1" daemon prio=5 tid=0x00007f9c92834800 nid=0xc103 in Object.wait() [0x0000000120f57000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000007d7b281b0> (a org.jminim.launch.Launcher$ConsoleThread)
at java.lang.Object.wait(Object.java:503)
at org.jminim.launch.Launcher$ConsoleThread.run(Launcher.java:1094)
- locked <0x00000007d7b281b0> (a org.jminim.launch.Launcher$ConsoleThread)

"AWT-EventQueue-0" prio=5 tid=0x00007f9c9182f800 nid=0xbf0f waiting on condition [0x0000000120e54000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000007d7cdfad0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Abst​ractQueuedSynchronizer.java:2043)
at java.awt.EventQueue.getNextEvent(EventQueue.java:543)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:211​)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150​)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

"Java2D Disposer" daemon prio=5 tid=0x00007f9c94043000 nid=0xbc03 in Object.wait() [0x0000000120d26000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
- locked <0x00000007d7b282b8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
at sun.java2d.Disposer.run(Disposer.java:145)
at java.lang.Thread.run(Thread.java:744)

"Java2D Queue Flusher" daemon prio=5 tid=0x00007f9c93883000 nid=0xb307 in Object.wait() [0x000000011e17d000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at sun.java2d.opengl.OGLRenderQueue$QueueFlusher.run(OGLRenderQueue.java:208)
- locked <0x00000007d7b13e38> (a sun.java2d.opengl.OGLRenderQueue$QueueFlusher)

"AWT-Shutdown" prio=5 tid=0x00007f9c9182c000 nid=0x7a07 in Object.wait() [0x000000011de8b000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:503)
at sun.awt.AWTAutoShutdown.run(AWTAutoShutdown.java:287)
- locked <0x00000007d7b28360> (a java.lang.Object)
at java.lang.Thread.run(Thread.java:744)

"AppKit Thread" daemon prio=5 tid=0x00007f9c92036000 nid=0x507 runnable [0x00007fff50456000]
java.lang.Thread.State: RUNNABLE
at sun.lwawt.macosx.LWCToolkit.doAWTRunLoop(Native Method)
at sun.lwawt.macosx.LWCToolkit.invokeAndWait(LWCToolkit.java:549)
at sun.lwawt.macosx.LWCToolkit.invokeAndWait(LWCToolkit.java:489)
at sun.lwawt.macosx.CAccessibility.invokeAndWait(CAccessibility.java:75)
at sun.lwawt.macosx.CAccessibility.getFocusOwner(CAccessibility.java:521)

"Service Thread" daemon prio=5 tid=0x00007f9c94825800 nid=0x5503 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"C2 CompilerThread1" daemon prio=5 tid=0x00007f9c93805800 nid=0x5303 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"C2 CompilerThread0" daemon prio=5 tid=0x00007f9c92804000 nid=0x5103 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Signal Dispatcher" daemon prio=5 tid=0x00007f9c94824800 nid=0x4f03 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE

"Finalizer" daemon prio=5 tid=0x00007f9c94006000 nid=0x3c03 in Object.wait() [0x000000011bdb0000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
- locked <0x00000007d7b44220> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:189)

"Reference Handler" daemon prio=5 tid=0x00007f9c93805000 nid=0x3a03 in Object.wait() [0x000000011bcad000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:503)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
- locked <0x00000007d7b442b8> (a java.lang.ref.Reference$Lock)

"main" prio=5 tid=0x00007f9c94804800 nid=0x1d03 in Object.wait() [0x0000000111552000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000007d7b44470> (a java.lang.Object)
at java.lang.Object.wait(Object.java:503)
at org.jminim.core.RuntimeImpl.waitForRequest(RuntimeImpl.java:2334)
- locked <0x00000007d7b44470> (a java.lang.Object)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:1229)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:808)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:81)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav​a:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jminim.launch.Launcher.doLaunch(Launcher.java:475)
at org.jminim.launch.Launcher.launch(Launcher.java:133)
at com.minimserver.watch.launch.LaunchWatch.main(LaunchWatch.java:28)

"VM Thread" prio=5 tid=0x00007f9c92801000 nid=0x3803 runnable

"GC task thread#0 (ParallelGC)" prio=5 tid=0x00007f9c94811800 nid=0x2203 runnable

"GC task thread#1 (ParallelGC)" prio=5 tid=0x00007f9c92800000 nid=0x2403 runnable

"GC task thread#2 (ParallelGC)" prio=5 tid=0x00007f9c93803800 nid=0x2603 runnable

"GC task thread#3 (ParallelGC)" prio=5 tid=0x00007f9c93804000 nid=0x2803 runnable

"GC task thread#4 (ParallelGC)" prio=5 tid=0x00007f9c94812000 nid=0x2a03 runnable

"GC task thread#5 (ParallelGC)" prio=5 tid=0x00007f9c94003000 nid=0x2c03 runnable

"GC task thread#6 (ParallelGC)" prio=5 tid=0x00007f9c95000000 nid=0x2e03 runnable

"GC task thread#7 (ParallelGC)" prio=5 tid=0x00007f9c95001000 nid=0x3003 runnable

"VM Periodic Task Thread" prio=5 tid=0x00007f9c9482e000 nid=0x5703 waiting on condition

JNI global references: 1866

axelk@plumplori ~$

[/font]
Find all posts by this user
Quote this message in a reply
28-02-2014, 15:32 (This post was last modified: 28-02-2014 15:37 by simoncn.)
Post: #8
RE: minimwatch hangs after update
(28-02-2014 13:39)axelk Wrote:  Hello Simon,

here is the jstack of the hanging JavaAppLauncher.

The problem seems to be here:

"AppKit Thread" daemon prio=5 tid=0x00007f9c92036000 nid=0x507 runnable [0x00007fff50456000]
java.lang.Thread.State: RUNNABLE
at sun.lwawt.macosx.LWCToolkit.doAWTRunLoop(Native Method)
at sun.lwawt.macosx.LWCToolkit.invokeAndWait(LWCToolkit.java:549)
at sun.lwawt.macosx.LWCToolkit.invokeAndWait(LWCToolkit.java:489)
at sun.lwawt.macosx.CAccessibility.invokeAndWait(CAccessibility.java:75)
at sun.lwawt.macosx.CAccessibility.getFocusOwner(CAccessibility.java:521)

It looks like this thread is in a loop. Do you see high CPU usage when the problem occurs?

I think the references to CAccessibility in this stack trace mean that Java accessibility support has been enabled. Have you changed any accessibility settings on the Mac, or are you using any other programs that might have done this?

Edit: This appears to be a known bug in Java. See this page for more information. Can you revert to Java 7u25 as suggested by one of the comments in the bug report?
Find all posts by this user
Quote this message in a reply
28-02-2014, 15:52
Post: #9
RE: minimwatch hangs after update
Quote:I think the references to CAccessibility in this stack trace mean that Java accessibility support has been enabled. Have you changed any accessibility settings on the Mac, or are you using any other programs that might have done this?

Edit: This appears to be a known bug in Java. See this page for more information. Can you revert to Java 7u25 as suggested by one of the comments in the bug report?

I think I found what is causing the problem. The word 'accessibility' remembered me that I did a change in the OSX-SystemPreferences-Accessibility to be able to use the utility 'TextExpander'. This utility is running all the time. When I stop TextExpander minim updates are working fine.

So watch out when you use TextExpander while updating minimserver :)


Many thanks for finding the cause !!

Axel
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)