-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When opening a file ran into StackOverflow and Eclipse asking to exit (on Eclipse 4.3.0 only?) #33
Comments
Thanks for the bug report Paul, and sorry about the bug.
|
Has baby grown up already ? :-) Will be great if you can devote some time again. |
Hi Paul,
Thank you &
|
At work and at home Windows 7 with Eclipse 4.3.x (above version is reported as 4.3.0) I have just tried again with 4.3.1 and it was OK. |
On 8 January 2014 09:24, Paul Verest [email protected] wrote:
Not quite -- but only a decade or so to go.
Best regards,
|
I think this issue should be opened with wontfix tag, so that users know they may need to update Eclipse. Otherwise README should be updated to say that there is bug on 4.3.0 |
Good point. - Dan On 23 January 2014 06:58, Paul Verest [email protected] wrote:
Dr Daniel Winterstein A: TechCube, Edinburgh, EH9 1PL |
I run in comparable issue (at least same stack according jvisualvm. Stil no StackOverflow due to 64bit JVM. I'm at eclipse 4.3.2v20140221... It happened today two times during Java comment source editing. |
@eremmel Can you reproduce now as of 2015 with Luna ? |
I don't have problem with https://raw.githubusercontent.com/felixge/node-mysql/master/Readme.md on Luna |
Maybe the file is too large. I guess. |
When opening a file below ran into StackOverflow and Eclipse asking to exit
https://github.com/felixge/node-mysql/blob/master/Readme.md
(Eclipse failed to start, only renaming project folder (thus making Readme.md unavailable) )
There is definitely circular calls, with no visible class to blame (stack too long).
eclipse.buildId=4.3.0.I20130605-2000
java.version=1.7.0_40
and so on
The text was updated successfully, but these errors were encountered: