| Summary: | [Compatibility] Team->History causes eclipse/java to hang/freeze (indefinitely?) | ||
|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | John <M8R-sgiphk> |
| Component: | UI | Assignee: | Remy Suen <remy.suen> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Remy Suen <remy.suen> |
| Severity: | critical | ||
| Priority: | P3 | CC: | bokowski, emoffatt, pwebster, remy.suen |
| Version: | unspecified | ||
| Target Milestone: | 4.1 M3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Attachments: | |||
|
Description
John
Created attachment 196221 [details]
stack trace (also known as thread dump)
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
apparently somewhere after some forced close(kill eclipse) this option got deselected: Window->Preferences->General->Appearance->Label Decorations->SVN and selecting it had no effect until after I restarted eclipse. Oh well, it's probably nothing ;) Created attachment 196720 [details]
another thread dump when got stuck / eclipse freeze
done in this eclipse:
Eclipse SDK
Version: 4.1.0
Build id: I20110526-1435
I thought it might be related to bug 344033 but that was "fixed" back in 04/28. PW John, you use secure storage to store your passwords, correct? Created attachment 196768 [details] SelectionService patch v1 Though @GroupUpdates is not working properly see (bug 342992 and bug 342994), moving forward I think we should let @GU handle post selection notifications. Right now we're sending out two post selection events for each selection call due to a listener chain. Removing the service's post selection listener on workbench parts will fix this problem. A post selection event is forwarded out consumers anyway when a regular selection is made so there should be no loss of functionality here. (In reply to comment #6) > Created attachment 196768 [details] > SelectionService patch v1 Patch released to CVS HEAD. John, please verify the fix when you get a chance, thanks. (In reply to comment #5) > John, you use secure storage to store your passwords, correct? I don't know, if I do it's without my knowledge(?) there are some settings there at least for that jme3 project with googlecode's location anyway bug seems to be fixed in: Eclipse SDK Version: 4.1.0 Build id: I20110526-2200 awesome! ;) (In reply to comment #8) > Build id: I20110526-2200 Actually, that build doesn't have my fix in it... :o (In reply to comment #9) > (In reply to comment #8) > > Build id: I20110526-2200 > > Actually, that build doesn't have my fix in it... :o I understand what you mean, it's a bit interesting since this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=346679 was 1 hour and 10 mins earlier and that seems to have been fixed, (unless I mis-tested it). I was guessing you probably initiated the build right after you patched that one, so this one was not in the probably-copied for build tree.. ok ignore Comment 10, I though I was posting on the other bug, but how come, since it doesn't have the fix... odd, probably I didn't do the test right? I don't get it xD I did notice that there was a SVN update with this eclipse (that build), since I installed them via Help->Check For Updates, possibly svn fixed it? I don't know... I will try to get the original build and retry the bug and make sure it does happen then come back to this build and test again, if it's indeed fixed and I'm reproducing it right (ie. missing mercurialeclipse atm, don't know if it's relevant) (In reply to comment #12) > I will try to get the original build and retry the bug and make sure it does > happen then come back to this build and test again, if it's indeed fixed and > I'm reproducing it right (ie. missing mercurialeclipse atm, don't know if it's > relevant) Hi John, thanks for your help. From what I understand, the Subversion plug-in is the only plug-in that's required to trigger the problem. Created attachment 196816 [details] these are the installed stuff in Eclipse SDK Version: 4.1.0 Build id: I20110526-2200 (In reply to comment #13) > Hi John, thanks for your help. From what I understand, the Subversion plug-in > is the only plug-in that's required to trigger the problem. Indeed it is so, and I tested bug again in: Eclipse SDK Version: 4.1.0 Build id: I20110518-2200 and it's there, then I updated only SVN stuff (see picture) and magically it's fixed, note: I had EGIT installed (all the time, if this matters) Anyway seems to me, the updated SVN stuff (even though dated earlier) did fix this bug or well it's no longer there... Let me know if I need to clarify more, Peace out:) oh dear, looks like something happened and eclipse got updated too (since I copy pasted the build id in prev comment), this means, eclipse and SVN stuff both got updated, I coulda sworn I chose only SVN stuff to be updated! I'll retry or something, then my previous comment means that bug got fixed when installing SVN updates and eclipse update to build: Eclipse SDK Version: 4.1.0 Build id: I20110526-2200 (In reply to comment #14) > Anyway seems to me, the updated SVN stuff (even though dated earlier) did fix > this bug or well it's no longer there... Hi John, I think it must have been from Subversive's fix for bug 313866. Thank you very much for your help. Please let us know if you encounter other problems using Eclipse 4.1. I have reverted the patch since Subversive has fixed the problem on their end. yeah, sorry about you having to dispose of the work you've done. I don't know about others but I personally do not appreciate when that happens. Cumulative is desired instead...or something along those lines. marked as resolved then .. Thank yous are implied :P |