Community
Participate
Working Groups
To reproduce: Create two Android library projects, ProjectOne and ProjectTwo. Right click on ProjectOne and select Properties->Android->Library->Add. ProjectTwo to the library reference. Then do the same thing to ProjectTwo, but add ProjectOne as the library. Eclipse will crash and the project.properties file needs to be modified in an external editor to resolve the issue. Attempting to modify project properties in Eclipse causes another crash.
Is there a crash/VM dump? Anything in the .log?
There probably was but it's long gone now. I can reproduce it if you'd like and post the logs/dump here. Just let me know what files you need and where I can find them after the crash.
(In reply to Aaron Wallace from comment #2) > There probably was but it's long gone now. > > I can reproduce it if you'd like and post the logs/dump here. Just let me > know what files you need and where I can find them after the crash. Usually the dumps are either as sibling of the eclipse.exe or the VM. Best would be to have a (small) test case.
Created attachment 243262 [details] Mac OSX crash report for this issue
for easier access, what seems to be the relevant slice: Crashed Thread: 0 AppKit Thread Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff5fb82fe8 VM Regions Near 0x7fff5fb82fe8: Stack 00007fff5f400000-00007fff5fb80000 [ 7680K] rw-/rwx SM=COW thread 0 --> Stack 00007fff5fb80000-00007fff5fb83000 [ 12K] ---/rwx SM=COW Stack 00007fff5fb83000-00007fff5fc00000 [ 500K] rw-/rwx SM=COW thread 0 Thread 0 Crashed:: AppKit Thread Dispatch queue: com.apple.main-thread 0 ??? 0x0000000108ed9260 0 + 4444754528 1 ??? 0x00000001082af158 0 + 4431999320 2 ??? 0x00000001082af158 0 + 4431999320 3 ??? 0x00000001082af333 0 + 4431999795 4 ??? 0x00000001082af333 0 + 4431999795 5 ??? 0x00000001082af158 0 + 4431999320 6 ??? 0x00000001082af158 0 + 4431999320 and so on up-to 511 ??? 0x00000001082af158 0 + 4431999320 Some native code, which doesn't give away its identity has gone into a deep recursion and then segfaulted. All we learn is the name of the thread: "AppKit Thread". Unless google finds a similar dump I don't see any clue of what is going on. Certainly not a bug in JDT/Core (which doesn't interface with any native code).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
