Previous Next Tracker index See it online !

(179/308) 1498 - MyDoggy: Deadlock on Project Change

Thread Dump provided.

Submitted	ezust - 2011-12-03 17:34:57	Assigned
Priority	5	Labels
Status	open	Group	None
Resolution	None

Comments

2011-12-03 17:34:58 ezust	deadlock-dump.txt (35.3Kio)
2011-12-04 08:46:03 *anonymous	Please try the fix here: http://community.jedit.org/?q=node/view/5011 and let me know if the issue is fixed. For technical reasons I could not update the git repository in SF. It's a new version of MyDoggy that is supposed to fix this deadlock.
2011-12-04 16:44:24 ezust	activity log activity.log (119.0Kio)
2011-12-04 16:44:52 ezust	Downloaded jar from community site. Was able to reproduce deadlock still. Got another thread dump and activity log for you.
2011-12-04 16:45:23 ezust	oops. sorry, ignore previous comment. I didn't replace the mydoggy jars.
2011-12-04 16:48:09 ezust	deadlock3 after replacing mydoggy jars deadlock-dump3.txt (29.6Kio)
2011-12-04 16:48:53 ezust	Ok, after replacing all the mydoggy jars, I still can reproduce easily. I just switch between 2 projects that have a few open .java files, and I am using java sidekick too. activity log and 3rd thread dump attached.
2012-01-28 20:07:27 ezust	- status: open --> closed-fixed
2012-01-28 20:07:27 ezust	Seems to be fixed in ProjectViewer 3.4.1. No longer can reproduce with Mydoggy (git trunk) version 0.3
2012-01-29 21:31:55 ezust	Reopening ticket. Attaching a more recent (deadlock4.txt) thread dump. jEdit 5.0pre1, MyDoggy 0.3, ProjectViewer 3.4.1
2012-01-29 21:31:55 ezust	- status: closed-fixed --> open
2012-01-29 21:32:16 ezust	mydoggy-deadlock4.txt (7.6Kio)
2012-01-30 07:05:25 jarekczek	Seems to me that Thread-4 is doing things that only EDT is allowed to do.
2012-02-29 20:46:36 *anonymous	- assigned_to: shlomy --> nobody