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.

Bug 51480 - Infinite "scanning" loop upon restart after IDE crash
Summary: Infinite "scanning" loop upon restart after IDE crash
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: Martin Matula
URL:
Keywords:
: 51154 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-11-13 00:36 UTC by Jan Chalupa
Modified: 2016-07-19 14:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
message.log file (86.61 KB, text/plain)
2004-11-13 00:37 UTC, Jan Chalupa
Details
message.log after fix (59.58 KB, text/plain)
2004-11-13 07:39 UTC, Jan Chalupa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Chalupa 2004-11-13 00:36:30 UTC
[fresh build of release40 as of 2004-11-13 0:00, 
JDK 1.5 b64]

My OS crashed while the IDE was running. After 
reboot and restart, the "scanning" dialog 
started flashing infinitely. The hard disk was 
thrashing all the time. I could see exceptions 
in the status bar (the IDE was run with 
netbeans.logger.console=false). I shut the IDE 
down using the window close button (x) and tried 
to restart again with exactly the same result.

Message log is full of exceptions of course. 
I'll attach it shortly.
Comment 1 Jan Chalupa 2004-11-13 00:37:54 UTC
Created attachment 18877 [details]
message.log file
Comment 2 Jan Chalupa 2004-11-13 07:39:08 UTC
Testing with the same userdir using javacore and mdr patches from mmatula:

After startup, the "scanning classpath" dialog appeared and the whole
project's classpath was rescanned. No infinite flashing and thrashing
this time. The IDE seemed to recover well. There were exceptions in
message.log (to be attached), but only from the first "recovery"
session. No more exceptions occurred on subseqent runs.

Looks good to me. I think this should go into 4.0, but don't know what
side-effects the fix may potentially have.
Comment 3 Jan Chalupa 2004-11-13 07:39:53 UTC
Created attachment 18881 [details]
message.log after fix
Comment 4 Jan Chalupa 2004-11-13 10:39:55 UTC
This is a serious problem. I'm raising the prioririty to P1 and
requesting a fix in the 'release40' branch. Please follow the high
resistance process.
Comment 5 Martin Matula 2004-11-13 10:53:35 UTC
Agreed. The second log looks OK. The fix is very simple (as I will
explain at reviewers@netbeans.org) and should not have any sideeffects.
Comment 6 Martin Matula 2004-11-13 10:59:14 UTC
Fixed in main trunk.

Checking in
mdr/src/org/netbeans/mdr/persistence/btreeimpl/btreestorage/BtreeDatabase.java;
/cvs/mdr/src/org/netbeans/mdr/persistence/btreeimpl/btreestorage/BtreeDatabase.java,v
 <--  BtreeDatabase.java
new revision: 1.25; previous revision: 1.24
done
Processing log script arguments...
More commits to come...
Checking in
java/javacore/src/org/netbeans/modules/javacore/JMManager.java;
/cvs/java/javacore/src/org/netbeans/modules/javacore/JMManager.java,v
 <--  JMManager.java
new revision: 1.75; previous revision: 1.74
done
Comment 8 Martin Matula 2004-11-15 09:29:03 UTC
Fix merged to release40.

Checking in
mdr/src/org/netbeans/mdr/persistence/btreeimpl/btreestorage/BtreeDatabase.java;
/cvs/mdr/src/org/netbeans/mdr/persistence/btreeimpl/btreestorage/BtreeDatabase.java,v
 <--  BtreeDatabase.java
new revision: 1.24.2.1; previous revision: 1.24
done
Processing log script arguments...
More commits to come...
Checking in
java/javacore/src/org/netbeans/modules/javacore/JMManager.java;
/cvs/java/javacore/src/org/netbeans/modules/javacore/JMManager.java,v
 <--  JMManager.java
new revision: 1.73.2.2; previous revision: 1.73.2.1
done
Comment 9 Martin Matula 2004-11-18 10:42:16 UTC
*** Issue 51154 has been marked as a duplicate of this issue. ***