This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Build: NetBeans IDE 6.0 Beta 2 (Build 200710212201) VM: Java HotSpot(TM) 64-Bit Server VM, 1.5.0_14-b03 OS: Windows Vista, 6.0, amd64 User Comments: may it's all related: 1. got crash of nb 2. load nb and all looks ok 3. restart windows 4. open nb java projects aren't opened (UML project is opened) and npe
Created attachment 53315 [details] stacktrace
after nb restart all projects are opened
What kind of crash are you refering in point 1. ? It's possible that during the crash your userdir got corrupted. Are you able to reproduce the issue or it happened just once?
never got it again, but crashes on 'clean-build' or 'build' happens sometimes yet
Please, provide more info about what do you mean by "crashes on 'clean-build' or 'build' happens sometimes yet". What kind of crashes? Thanks.
we discussed it in uml team just before release, and most team member reported they have crahes on bulding. with latest builds it seems less important(may be because some additional checks for filesytem problem was implemented, I start getting yyy.jar can't be found sometimes with next build was able to find this jar, can't be certain now, if I'll get again, I'll try to update the issue) but still happens sometimes, just invoke 'clean/build on uml module project after some work with classes and ide disappears. I'm on holiday break until January 9, so have no crashes at all now
If the IDE crashes, it looks more like a problem of JDK. NetBeans, of course cannot restore opened projects then. Is there any JDK dump after the crash?
Where I can get jdk dump? I'll search next time ide will crash or may be there is old one somewhere
I think that it's usually in netbeans bin folder (along with the executable that launched ide).
ok, I found one jvm log in nb folder, but don't remember if it was in time of last crash may be this issue can be resolved as invalid/works for me because even with first good load after crash it still may be related to crash which may cause any problem and I also saw it only once I can file separate issue for crashes next time it occur(of cause this issue may be dependent on jvm issue, but still an issue)
OK, thanks for info. I'll close the issue. If you got crash again please file new issue (also consider that it might be JVM problem).