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.
Summary: | ant fails, netbeans blocked | ||
---|---|---|---|
Product: | projects | Reporter: | drscott <drscott> |
Component: | Ant | Assignee: | issues@projects <issues> |
Status: | VERIFIED WONTFIX | ||
Severity: | blocker | Keywords: | JDK_SPECIFIC |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
ide.log
threat dump |
Description
drscott
2003-05-09 15:34:58 UTC
Hmm, I can't reproduce any such problem on Linux, JDK 1.4.2 beta, using 35 RC1 and sources from CVS in release35 branch (very nearly the same as the downloaded sources for 35 RC1). I started in a fresh user dir using -J-Dnetbeans.logger.console=true just in case any errors (e.g. OutOfMemoryError) were printed; mounted /space/src/r35 (cancelling code completion on it of course); then did build, tryme, clean, build. All ran fine. Maybe a WinXP problem? DrScott, if this happens again please: 1. Attach your ide.log file. Perhaps there is some error message. In the case of an OutOfMemoryError, it is actually wise to turn on console logging and use runide.exe not runidew.exe, so you can see any errors immediately. 2. If the IDE seems frozen or sluggish, get a thread dump (Ctrl-Break) and attach that too. Lowering prio to P3, since there is no reproducible testcase. If you think it's really P2 problem please provide feedback which mentioned Jesse. Thanks. Created attachment 10264 [details]
ide.log
Created attachment 10265 [details]
threat dump
[This referes to the attatchments above] Sorry for the delay, but my system is at work and i can not access it during the weekend. Yes, it was reproducable for me when i reported the bug, so i tried to get the information you asked for. But now, i have problems to reproduce it due to another issue: I do: 1. target 'build' 2. target 'clean' After a while, ant fails with this error message: nbbuild\build.xml [1.021] Unable to delete file D:\project\netbeans-src-hola\core\netbeans\lib\ext\boot.jar BUILD FAILED where D:\project\netbeans-src-hola\ is the root where i stored the source. Hmm, ant tells the truth: i am not able to delete that file manually (...locked by another process...). So i used a tool called 'procexp.exe' to find that process: It's netbeans itsself! 'procexp' has the ability to force 'unlocking' of such files, and so i did. But target 'clean' failed again with nearly the same message, now it's file 'openide.jar' (from the source directory). I repeat this step also for the following files: openide-13javac-workaround.jar openidex.jar vcscore.jar (all files located within source directory, _not_ Netbeans installation directory!) Again target 'clean'... Now the 'real' bug occoured again: Netbeans is totaly frozen (this time, status bar mention 'ant running', but again the execution view is gone). So, finally i am able to give you the wanted information. Re. locks - this has nothing to do with NetBeans as such; running Ant can lock JAR files it creates (on Windows) for the duration of the VM session, especially Javac which in older JDKs is bad about releasing file locks when it is done compiling. (I would strongly advise an upgrade to JDK 1.4.) Re. ide.log & thread dump - log shows no errors, and thread dump shows no activity whatsoever, so I have no further suggestions. Maybe someone who runs Windows can figure out what is going on if the problem is independently reproducible. I still suspect an OutOfMemoryError - this might *not* appear in the ide.log file, since the act of logging it itself requires some heap, which is why I suggested that the raw runide.exe console output be attached rather than the log file. I ran it from the console using runide.exe. But there was abolutely no output (except for the thread dump later...) Sorry didn't mentioned it. I would like to help debugging that problem if somebody tells me how to do. (How/where to gain information why ant is suddenly dying? I think that it dies because the process indicator is removed from the execution view and then that view is closed too.) I don't belive in out of memory: I've set -Xmx256M. Should be enough? Sorry I failed to emphasize - you must pass the command-line argument -J-Dnetbeans.logger.console=true to get output to the console in a NB release build. (Dev builds have this on by default.) 256Mb heap sounds like more than enough. I run with 196 usually (have a lot of RAM, may as well) and do a lot of Ant builds without problems. Sorry, no tips for figuring out what is dying. Normally when a Java app freezes, you can look at the thread dump and figure out why. In this case the thread dump does not show any activity at all, as if it were idle. ok, now i reproduced the bug while having -J- Dnetbeans.logger.console=true set. Unfortunately no error messages. Last output on console (which appears right after nb is up and running...): Starting system in full screen (MDI) UI mode. Anyway, some news: I can reproduce the problem only by running jsdk1.3.1 (i use build 1.3.1_04-b02). Using 141 does not show the bug. Can be similar to issue 25753. It also happened on 1.3.x only, but later it appeared also on 1.4.x but less frequently. JDK 1.3 will not be supported for NetBeans 3.6 anyway. It requires JDK 1.4+. closed |