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.
Do not know how I got ide into this state, but I am able to reproduce it using following steps: 1.unzip fresh build of NB32 and start it 2.install apisupport 3.mount attached directory 4.exit ide 5.put attached jar into {ide_home}/lib/patches //there were patched some classes to dumping stack 6.overwrite in installedModules.xml and externalizedModules.ser in {userdir}/modules by attached ones 7.start ide 8.expand the mounted directory from the step 3. 9.infinite calling of refresh starts, see terminal window This causes that the ide is unusable because of high cpu load and long time to expand folders in the explorer. Can be solved by disabling and reenabling apisupport module.
Created attachment 1268 [details] dir.jar - unpack and mount the apiexamples dir in the step 3.
Created attachment 1269 [details] traces.jar - add to {nbhome}/lib/patches in the step 5.
Created attachment 1270 [details] externalizedModules.ser for step 6
Created attachment 1271 [details] installedModules.xml for step 6
Fixed in main trunk. Attached updater.jar with patch follows:
Sorry, my previous comment was done by mistake. I thought that is another bug :-) So its NOT FIXED!
Created attachment 1292 [details] Simpler directory to test - apiexamples.zip
Target milestone -> 3.3
There is incorrect order of dataloaders. ModuleDataLoader should be before JARDataLoader in order. e.g. if you change this order in Object Types problem disappear. However there is a bug appeared in such situation. I tried to fix it - seems OK, patch for testing is attached.
Created attachment 1371 [details] Patch for DataObjectPool
More detail from Ales; may help understand loader fix needed for 12179: In 11810 was following problem: 1. JARDataLoader was in order of dataloaders (visible in ObjectTypes) before ModuleDataLoader 2. x.jarContent was recognized by JARDataLoader. 3. ModuleDataLoader tries to recognize x-test.jar, which has primary file x.jarContent, so MDL tries to revalidate it. But because of order x.jarContent is recognized by JARDataLoader again. 4. And there is a bug because tring to recognize this file again .. and again My fix should fix the problem without change DL order, (avoid step 4.), but this x.jarContent won't be recognize with ModuleDataLoader without changing order of loaders.
Fixed in main trunk.
verified in the trunk, the problem doesn't seem to appear any more
Diff: http://www.netbeans.org/unbranded- source/browse/openide/src/org/openide/loaders/DataObjectPool.java.diff? r1=1.36&r2=1.37
Fixed in pilsen_fcs
Adjusting target milestone.
Resolved for 3.4.x or earlier, no new info since then -> closing.