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: | Do not load classes on startup | ||
---|---|---|---|
Product: | java | Reporter: | Jaroslav Tulach <jtulach> |
Component: | Unsupported | Assignee: | issues@java <issues> |
Status: | CLOSED INVALID | ||
Severity: | blocker | Keywords: | PERFORMANCE |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 21676 |
Description
Jaroslav Tulach
2002-03-28 16:45:13 UTC
I don't understand why this is P2 issue. Lowering priority. Because of the keyword PERF? Is not performance important to you? Are not you interested in knowning why the hell JavaCompilerType is initialized on startup? I'll be really glad if you could find out why the class is loaded into the VM. I am searching for list of ways how a class can be loaded during startup and I need your help. Invalid; java.environment* classes are loaded on behalf of the AutoMounter support in core when it recognizes module-provided JARs that are registered in the layer. The CompilerType is not loaded on the startup, but rather at the first query for the compiler. Since Java nodes need to check up-to-date state to properly badge their icon, it can happen quite early - when a Java node appears on screen. If unhappy, please disable "Show Compile Status" in Java sources. Resolved for 3.4.x or earlier, no new info since then -> closing. Resolved for 3.4.x or earlier, no new info since then -> closing. |