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.
dev build 200501311900 JDK 1.5.0_01 Installation hangs at "8% Building storage". CPU usage averages at 10% but it never terminates (I waited a long while).
There was problem with hanging storage builder during installation but it was fixed 26 Jan. So in build from 31 Jan it should be ok. Is it reproducible? I will try to reproduce this.
Actually it DOES install, but it takes ages. I've tried with builds 200502021900 and 200502031900. It almost hangs with java.exe taking 99% of processor usage, probably when executing file run-storage- builder-windows.bat.
Created attachment 20206 [details] install.log
Created attachment 20207 [details] storagebuilder.log
There has to be a bug here. The first time the classpath is parsed in 4.0 it takes a while on my machine, but not *that* long. Why is the performance so poor during installation time?
If it does not hang it is ok. The reason why it takes so long is it parses whole src.zip. We know about it and it will be shortened by selecting only subset to parse. (Storage builder run takes long time even when run separately and it takes even longer when run in installer.) Just today I changed parsing not to do full parsing of src.zip from JDK so it is much faster. In the end it should parse only most used classes from JDK. Difference is that in IDE parser does much less work than in installer so far. But as I said just today I changed it so that it should do the same as in IDE.
Marek, Can we add a "estimated time left" indicator? This process is very long (even in the IDE) and now that we have moved it into the installer I think people would appreciate some sort of ETA. The progress indicator isn't really useful in this case because it takes so long the indicator takes a while to show a noticable change. I for one would prefer an ETA indicator over a percentage complete. Can we reopen this issue as a RFE?
Yes you can reopen this issue as RFE. But I expect that after some tuning of amount of parsed code it will become shorter so it will not require changes in UI you propose.
This RFE looks for either better substantially classpath parsing performance or a ETA display.
Currently parsing of JDK sources is done during installation panel. It is UI requirement to have just one progress dialog as user do not need to select Next button 2 times. Standard progress dialog shows percentage completed. This cannot be changed. We can display text ETA but this will be very rough approximation based on percentage of data size already generated by parsing. I can estimate remaining from first 5% data generated then 10% and so on. In addition function between time and data size need not be linear. Petr what do you think?
According to our discussion I agree with displayng ETA text below progress bar.
Passing to nbi for evaluation. It might be good if there is some long task during installation. AFAIK JDK sources are not now preparsed during installation. On the other hand jars are unpacked. If it is possible to estimate time left it could be good to add text info with ETA to progress bar. Typical example is download progress in browser.
*** This issue has been marked as a duplicate of 88038 ***