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: | Netbeans holds jar files unnecessarily | ||
---|---|---|---|
Product: | platform | Reporter: | Falchion14 |
Component: | Filesystems | Assignee: | Tomas Hurka <thurka> |
Status: | REOPENED --- | ||
Severity: | normal | CC: | jlahoda, thurka |
Priority: | P3 | ||
Version: | 7.4 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Falchion14
2012-10-03 15:36:20 UTC
Recently there was similar report, I guess. It turned out not to be a bug in filesystems. If it is not a bug, it seems like an opportunity to improve that would help some Windows users. Thanks for looking into this! (In reply to comment #2) > If it is not a bug, it seems like an opportunity to improve that would help > some Windows users. Thanks for looking into this! I would like to investigate it, but first try the latest NetBeans dev. build. If you can still reproduce it with the latest dev. build, please provide exact steps how to reproduce it. Thanks. (Updated to 7.3 as that is where we currently are using.) This problem has continued to plague us, but I don't have a good way to reproduce it. However, I do have a theory that seems to match what I'm seeing and why I can't reproduce it in a small test case. We have 18 projects and probably more than 2 dozen jars. When we start an external top level clean and build our Ant script goes through each project and calls "clean" on that project's build.xml. This alone takes a few seconds. After a few jar files are deleted, it seems NetBeans wakes up and realizes that some jar files in the dist directories have been removed. So it starts the background scanning of projects. Right after that, my Ant script fails because we couldn't delete a dist/jar file. Now, I wait until the Background Scanning completes (a few more seconds) and then click on the NetBeans' Memory graph to force garbage collection. Now I can restart the top level build script and it will successfully clean the remaining jars before the next Background Scanning kicks off. So, it seems to me that my problem is caused by the Background Scanning kicking off during the middle of an external cleaning of the projects. The Background Scanning is looking at the deleted jars and the remaining jars and in doing so locks the remaining jars so that Ant fails when it tries to delete them. Does that seem reasonable? Is there a good workaround, besides what I outlined above (i.e. something less manual)? Other thoughts? I won't reopen this unless I don't get a response after sometime, as I think my report is still incomplete, though I'm at a loss how to simply reproduce the problem. Maybe someone else has a thought on how to test my hypothesis. Reopening in hopes of getting a response. This behavior is reproducible by running clean and build inside NetBeans on a specific project while a Background Scan is in progress. (In reply to Falchion14 from comment #6) > This behavior is reproducible by running clean and build inside NetBeans on > a specific project while a Background Scan is in progress. Or maybe not. Looks like it was a slightly different problem where something actually was using the jar besides the Background Scan. Problem also exists on NetBeans 7.4. Marking the issue accordingly. |