Bugzilla – Full Text Bug Listing
| Summary: | Eclipse hangs when pressing Ctrl+Space | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | DonMartio <donmartio> |
| Component: | PDT | Assignee: | PHP Core <php.core-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | CC: | brenden, donmartio, gadi, marek78uk, spektom |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
Updated to 2.1.2 and the Problem remains. Changed the jvm from 1.6 to 1.5 and back but nothing changes. If someone can tell me what's happing if i press Ctrl+Space i may can track it down myself. *** Bug 261677 has been marked as a duplicate of this bug. *** Same here: when I press Ctrl+Space PDT editor hangs for few seconds, if I keep typing, it will print all characters I've typed. Ok, next move. I tried a new eclipse installation. All fresh and new. I deleted .settings and all the other .*** Files in one off my projects. After the first Build i tried Ctrl+Space an after a second the Context-Dropdown appeared. I was lucky for a fraction of a second until eclipse completely crashes. I found a file hs_err_pid16411.log in my home dirctory which is full of stuff and i recognized this int the trace: Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [libxul.so+0xa2d855] C [libxul.so+0xa2dd05] C [libxul.so+0xa35370] NS_NewLocalFile_P+0x30 C [libxpcom.so+0x2ad8] NS_NewLocalFile+0x20 C [libswt-mozilla-gtk-3550.so+0x6862] Java_org_eclipse_swt_internal_mozilla_XPCOM__1NS_1NewLocalFile+0x52 Since xulrunner was realy generous in the past when it comes to causing problems i reemerged it (i am using gentoo) and nss (there was a hint about that). Andnow i am at the same point as before. Eclipse hangs when pressing Ctrl+Space so i have to kill it. It's a little bit strange that this only happens in a pdt Editor. If this isn't a bug related to pdt maybe someon can give me a hint where to look for or how to get rid of this xulrunner mess. Just for the record i'm using a downloaded Version of eclipse, not the ebuild that comes with gentoo. Fixed in 2.2.0. (In reply to comment #5) > Fixed in 2.2.0. Cool, when will 2.2.0 be published? Well i saw this on the Projectpage: Schedule (see also Project Plan): 21st of June, 2010 - PDT 2.2 Release Is there any possibility to get this fix earlier? This bug is realy anoying. No, there's no possibility, since a bug was actually in DLTK indexing infrastructure. PDT 2.2 is the only version compatible with updated DLTK 2.0. For a while please use PDT 2.2.0 integration builds. Ok, sounds good, besides i can't get it installed. I tried it using the dropins folder but that doesn't work. Is there a howto/walkthroiugh/whatever for installing integration build? Please open another bug regarding installation of integration build. *** Bug 290573 has been marked as a duplicate of this bug. *** Te-tested in PDT 2.2.0 20091203-1849 - verified fixed. Kalin Yanev kalin.a@zend.com |
Everytime when i hit Ctrl+Space Eclipse Hangs. When i do strace -p on the eclipse Process it is waiting for some Thread and never returns. ~ $ strace -p 3362 Process 3362 attached - interrupt to quit futex(0xb72b2bd8, FUTEX_WAIT, 3366, NULL This Prozess 3366 sems to be a thread. I can't see it using ps. But i can strace it: ~ $ strace -p 3366 Process 3366 attached - interrupt to quit restart_syscall(<... resuming interrupted call ...>) = -1 ETIMEDOUT (Connection timed out) futex(0x8058128, FUTEX_WAKE_PRIVATE, 1) = 0 clock_gettime(CLOCK_MONOTONIC, {95499, 36835014}) = 0 clock_gettime(CLOCK_MONOTONIC, {95499, 36883960}) = 0 clock_gettime(CLOCK_MONOTONIC, {95499, 36913059}) = 0 gettimeofday({1251811937, 658859}, NULL) = 0 clock_gettime(CLOCK_REALTIME, {1251811937, 658898145}) = 0 futex(0x7f5c135c, FUTEX_WAIT_PRIVATE, 1, {0, 49960855}) = -1 ETIMEDOUT (Connection timed out) futex(0x8058128, FUTEX_WAKE_PRIVATE, 1) = 0 clock_gettime(CLOCK_MONOTONIC, {95499, 87123594}) = 0 clock_gettime(CLOCK_MONOTONIC, {95499, 87162221}) = 0 clock_gettime(CLOCK_MONOTONIC, {95499, 87191421}) = 0 gettimeofday({1251811937, 709136}, NULL) = 0 clock_gettime(CLOCK_REALTIME, {1251811937, 709168991}) = 0 futex(0x7f5c135c, FUTEX_WAIT_PRIVATE, 1, {0, 49967009}) = -1 ETIMEDOUT (Connection timed out) ..... This is coming until i kill eclipse.