Bug 335819

Comment 1 Lars Sonchocky-Helldorf 2011-01-31 04:56:57 EST

Created attachment 187940 [details]
crash log for this bug

the crash log as provided by the Mac OS X build in crash catcher

Comment 2 Alexander Gurov 2011-02-01 00:57:52 EST

It looks like the issue is unrelated to the Subversive plug-in itself. Please check the crashed thread:

Thread 0 Crashed:
0   com.apple.CoreFoundation      	0x00007fff80cb42e1 __HALT + 1
1   com.apple.CoreFoundation      	0x00007fff80d19cbb CFSetRemoveValue + 715
2   com.apple.AppKit              	0x00007fff82e80733 removeChildRowEntries + 331
3   com.apple.AppKit              	0x00007fff82e80741 removeChildRowEntries + 345
4   com.apple.AppKit              	0x00007fff82e7e018 -[NSOutlineView reloadItem:reloadChildren:] + 597
5   libswt-pi-cocoa-3655.jnilib   	0x000000014c7e0762 Java_org_eclipse_swt_internal_cocoa_OS_objc_1msgSend__JJJZ + 64

It definitely points to the SWT library code, which is crashed.

If you can prove that the situation is caused by the Subversive code, then please provide more information regarding crash case (like steps to reproduce, screenshots of what happened directly before crash etc.).
And one more note: it is always safer to use Java libraries instead of native ones. So, if you're using JavaHL connector, you can switch to the SVN Kit-based one.

P.S.
Also please note that we have no access to the Apple hardware/software (in our region it is something like rare animal :) ), so we can't reproduce Mac-related issues on our own.

Comment 3 Lars Sonchocky-Helldorf 2011-03-04 17:06:27 EST

@Alexander Gurow

Why do you – after you realized it's NOT an subversive bug but a SWT bug – just close it instead of forwarding it to the right product and component? You could at least have reset it to Product "Platform" and not close it as "WORKSFORME" because it doesn't work for you (since you could not try on your own as you stated in your comment).

Btw. I filed the bug for the "Team" component and the "Platform" product, it was changed to "Subversive" by Szymon Brandys <Szymon.Brandys@pl.ibm.com>

So please be so kind and reopen this bug (I can't do this, I havent the rights for this) and forward it to the right place.

Thanks,

    Lars

Comment 4 Alexander Gurov 2011-03-08 11:04:53 EST

Please don't feel offended, I can reopen it, but who will fix it then? 

When you say "I had committed my source code with Subversive and it crashed my Eclipse", of course anyone would say for the start: let's ask Subversive project's guys. All right, that is the case and I've checked crash dump and found out - it is not the Subversive code, that caused the crash. Yes, I've closed the issue report as "works for me", but still asked you about additional information, steps to reproduce, given some advices regarding how you could try to avoid the issue. And what we get in the end?
1) Reproducible: Didn't try
2) Subversive version - unknown
3) Which connector were used - unknown
4) Is this RCP, PDT, FlexBuilder or whatever - unknow
5) On which stage it was crashed?
6) Were there any parallel jobs outside commit?
etc., etc., etc.

There is no information at all. Even if I move the issue to the Platform or any other component, do you think they have any chances with this much information available?
I don't even know who is responsible for the code pointed by "com.apple.CoreFoundation" is it the "Apple" company? Can I force the "Apple" company to fix it?

P.S.
I would gladly reopen the issue and move it to the Platform component or somewhere else were we can get some advices on how to solve the issue, but could you please provide at least a little more information for those who will look into the problem?