Community
Participate
Working Groups
I downloaded the 3.0 M1 build, and used it with the same old workspace that I had before. Everything was working fine, till after a few hours, all of a sudden I kept getting errors. I wlll attach the .log file
Created attachment 5118 [details] .log file
Even after deleting a couple of times, I still got the error. Finally, I just rebooted the machine, and it started working - maybe there is a thread that was still changing files?
Not SWT.
"Even after deleting a couple of times, I still got the error" Deleting what? The workspace? And what error messsage did you get in the user interface? Thanks.
Not sure if its the same, but similar anyway: I'm working with eclipse 2.1 on a Linux machine using the blackdown-jdk. I copied the workspace from another machine where the same eclipse build ran since 2.1 was released without problems (with sun jdk). I got freezes on different ways, I'm reporting 2 of it that could reproduce: 1. I worked for some hours without problems, then I created javadocs in the project directory of the current project. Next time I started eclipse (after a reboot) I wanted to create javadocs again into the same directory. After choosing export -> javadoc, click on <next> the assistant froze. I could close the assistant window with <x> but the only thing that reacted in the eclipse main window was the <x> again, which brought the question "Exit <yes> <no>" but that did not work (buttons didn't work at all, so maybe that's just a natural prosecution. A thing I noticed is that when eclipse freezes that way, X uses 100% processor time, exactly so long until I kill eclipse. Killing eclipse and deleting the javadoc folder made it work again, but only until the next restart. having the javadoc target folder outside the workspace seemed to work, but I couldn't test it really, because the next topic prevents me from testing anything any more: 2. I don't exactly remember what my last action was, before it happened, it was just something I do all the time. Since then, on my current project, arbitrary imports from other packages in the same project are marked as "could not be resolved". Example, in a class outside com.schneide.quantity The first 2 lines are all ok, the third is marked as "could not be resolved" import com.schneide.quantity.AbstractQuantity import com.schneide.quantity.CompoundUnit import com.schneide.quantity.WrongUnitException where WrongUnitException itself is shown with no Errors, but AbstractQuantity and CompoundUnit itself can not resolve some types. Before that all-day action since which I have the error, the whole project was compiled fine. Now, since these errors are shown, I can not do any action that involves showing new dialogs, as soon as one comes up, eclipse freezes, the dialog itself stays half painted. Until I open a dialog, I can use the editor and open and close packages and classes, but I can not scroll down in the package explorer. From the startup on, X then uses 65-70% of processor power, Java the remaining. Eclipse itself works fine with new workspaces. I copied the workspace back to the old machine where everything stayed fine. I suppose it may have to do something with the blackdown jdk and I'm now in the process of installing the sun jdk but it may take some days until I can test it. Those errors don't write anything into the .log file which stayed empty after I emptied it before trying to reproduce the errors.
Yes - I had to delete the workspace and recreate from scratch. I dont remember what error message showed up.
Mathias, the problems you reported do not look related to this one. Please open different PRs against each different problem you have. Also, if you have a reproducible test case, it is much more likely that the problems will be fixed. Thanks. Moving to Platform/UI for comments, which is the only other component involved in the Arithmetic/InvalidArgumentException stack traces (since it has been said it is not SWT).
well, either way. I can not reproduce my problems with the sun jdk, so I am just happy with it now.
Closing as per last comments.
Please do not close the bug if the original reporter has not put in comments saying that this now works! This bug seems to have been marked as resolved based on comments from a different person who was reporting some OTHER bugs. Anyway, I still appreciate the work being done, and this bug does not seem to be raising it ugly head any more.
This bug has been closed for almost a year now. If you do experience this problem, it is more useful to open a new PR anyway.
Closing
