Community
Participate
Working Groups
Build Identifier: Version: 3.7.0 Build id: I20110613-1736 I'm running Eclispe SDK v3.7 on MAC OS lion 10.7.3, Eclipse crashes usually when I try to commit the project (it's an SVN project), but it happens when I try to open some file of the project. The extension that I'm using is Aptana Studio. See the error message in attachment. Reproducible: Couldn't Reproduce
Created attachment 210632 [details] eclipse crash report
Yes, it's crashed in time of Subversive activity, but it seems it is crashed while forming call stack for the plain Java method call (there are no interaction with the native code or anything else that could affect JVM): Current thread (1160b5000): JavaThread "SVN-FUB6K" [_thread_in_vm, id=293605376, stack(111701000,111801000)] Stack: [111701000,111801000] Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j org.tmatesoft.svn.core.ISVNCanceller.<clinit>()V+0 v ~StubRoutines::call_stub j org.tmatesoft.svn.core.internal.util.SVNSocketFactory.connect(Ljava/net/Socket;Ljava/net/InetSocketAddress;ILorg/tmatesoft/svn/core/ISVNCanceller;)V+5 So, to me it seems like a JVM issue. Also if it crashes not only in time of Subversive activity, but while opening a file too, then the more reason to me is to blame the JVM (since I doubt Macintosh could be overclocked and have hardware instabilities as a result). Unfortunately I can't give you any useful advices except checking for a newer JVM versions.
Hi Alexander, unfortunately it's not so easy to update manually JVM for mac osx, because even java.com tells you to use apple software update. Do you have any further suggestion about how to set up Eclipse or any other stuff that could help me? Thank you in advance.
(In reply to comment #2) > Yes, it's crashed in time of Subversive activity, but it seems it is crashed > while forming call stack for the plain Java method call (there are no > interaction with the native code or anything else that could affect JVM): > > Current thread (1160b5000): JavaThread "SVN-FUB6K" [_thread_in_vm, > id=293605376, stack(111701000,111801000)] > Stack: [111701000,111801000] > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j org.tmatesoft.svn.core.ISVNCanceller.<clinit>()V+0 > v ~StubRoutines::call_stub > j > org.tmatesoft.svn.core.internal.util.SVNSocketFactory.connect(Ljava/net/Socket;Ljava/net/InetSocketAddress;ILorg/tmatesoft/svn/core/ISVNCanceller;)V+5 > > So, to me it seems like a JVM issue. Also if it crashes not only in time of > Subversive activity, but while opening a file too, then the more reason to me > is to blame the JVM (since I doubt Macintosh could be overclocked and have > hardware instabilities as a result). > > Unfortunately I can't give you any useful advices except checking for a newer > JVM versions. Hi Alexander, unfortunately it's not so easy to update manually JVM for mac osx, because even java.com tells you to use apple software update. Do you have any further suggestion about how to set up Eclipse or any other stuff that could help me? Thank you in advance.
(In reply to comment #3) > Hi Alexander, > unfortunately it's not so easy to update manually JVM for mac osx, because even > java.com tells you to use apple software update. Do you have any further > suggestion about how to set up Eclipse or any other stuff that could help me? > Thank you in advance. That is an unfortunate situation. And since in my region a Mac computer is a rare species I've never ever seen one in real life, so I can't think of any useful suggestions. I've tried to google for a similar issues, but the closest one I found was this: http://www.exelisvis.com/language/en-US/Support/HelpArticleDetail/articleid/4698.aspx?dnnprintmode=true&mid=6229&SkinSrc=[G]Skins%2F_default%2FNo+Skin&ContainerSrc=[G]Containers%2F_default%2FNo+Container and it does not seem to be related since it is caused by some native library at Eclipse startup which obviously is not your situation. P.S. Oh, I think there is one thing you may try (I'm not sure if it possible or even reasonable, but still...): since the cause is SIGSEGV it could be due to program memory damaged by some native code running within the JVM boundries. For example SWT support or something around those lines. If that is the case then updating Eclipse could possibly help the situation.
