Welcome! Log In Create A New Profile

Advanced

Detected Deadlock in UI Thread

Posted by emorkay 
Detected Deadlock in UI Thread
January 20, 2011 03:56PM
Hi,
I am using Jucy v0.85 64-bit in Ubuntu 10.10 64-bit on my laptop. Whenever I try to connect to a hub, Jucy complains that "Deadlock is detected in UI Thread" and becomes unresponsive for quite sometime and at times it kills the JVM and exits. Has it got something to do with the version of JRE installed in my laptop? I currently have Sun JRE v 1.6_22 64-bit installed in my laptop.

Could you please tell me what the problem is and how I can fix it?

Appreciate any help in this regard.

Thanks,
Re: Detected Deadlock in UI Thread
January 20, 2011 09:49PM
Can you give me the logs .. see here: [jucy.eu] for more detail

------------------------------------------------------------------------
Freedom is a new religion, the religion of our time.
- Heinrich Heine
Re: Detected Deadlock in UI Thread
January 21, 2011 01:18PM
Hi,
The logs are at the following locations.

error.log: [pastebin.com]

.metadata/.log: [pastebin.com]

With the little Java programming experience I have and from the logs, I guess the JVM is running out of memory when Jucy is launched.

Let me know if that's indeed what's causing the trouble.

Thanks,
Re: Detected Deadlock in UI Thread
January 21, 2011 07:02PM
Also the memory error might cause strange behaviour of any kind... and this deadlock looks kind of strange.
Maybe you could try adding some memory .. as 64 Bit system consume nearly double the memory. In combination with generally large memory requirements this might be problematic.

Just look for the .ini file next to jucy's executable.. change the Xmx value to something higher.

------------------------------------------------------------------------
Freedom is a new religion, the religion of our time.
- Heinrich Heine
Re: Detected Deadlock in UI Thread
January 23, 2011 07:50AM
Hi,

I tried increasing the Xmx value to 1024m but the problem still persists.

Anything else that we can do to fix this?

Thanks,
Re: Detected Deadlock in UI Thread
January 23, 2011 11:41AM
2. things

1. Download jucy anew and unpack it again (not over the existing install).. maybe something got damadged / or maybe some update did not work out correctly


2. if you have JDK installed you could start jconsole connect to jucy and create a heapdump. (under MBeans -> com.sun.management -> HotSpotDiagnostics-> Operations (1. args needs a path to where to store the dump))
A heapdump would help me to see where the this memory vasnished to.

------------------------------------------------------------------------
Freedom is a new religion, the religion of our time.
- Heinrich Heine



Edited 1 time(s). Last edit at 01/23/2011 11:42AM by Quicksilver.
Sorry, only registered users may post in this forum.

Click here to login