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.
Profiler 070221 NetBeans IDE Dev (Build 200702201900) 1.5.0_10; Java HotSpot(TM) Client VM 1.5.0_10-b03 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251 Steps to reproduce: - Perform Analyze Performance Profiling of Anagram Game - Open VM Telemetry, VM Telemetry Overview, Live Results, Snapshot, Threads windows - Close IDE - Uninstall Profiler - Start IDE - RESULT: Exceptions are thrown. During first start up they will be shown to the user, on successive start ups exceptions are shown only in log. java.io.IOException: Top component PROFILERTELEMETRYOVERVIEW_TC could not be loaded, either owning module was disabled, has incompatible version or top components settings file format is broken. at org.netbeans.core.windows.persistence.PersistenceManager.getTopComponentPersistentForID(PersistenceManager.java:497) ... java.io.IOException: Top component PROFILERCONTROLPANEL_TC could not be loaded, either owning module was disabled, has incompatible version or top components settings file format is broken. at org.netbeans.core.windows.persistence.PersistenceManager.getTopComponentPersistentForID(PersistenceManager.java:497) ... java.io.IOException: Top component PROFILERCONTROLPANEL_TC could not be loaded, either owning module was disabled, has incompatible version or top components settings file format is broken. at org.netbeans.core.windows.persistence.PersistenceManager.getTopComponentPersistentForID(PersistenceManager.java:497) ... java.io.IOException: Top component PROFILERTELEMETRYOVERVIEW_TC could not be loaded, either owning module was disabled, has incompatible version or top components settings file format is broken. at org.netbeans.core.windows.persistence.PersistenceManager.getTopComponentPersistentForID(PersistenceManager.java:497) ...
Created attachment 38774 [details] Exceptions
Created attachment 38775 [details] Messages.log on first run
Created attachment 38777 [details] Messages.log on 3rd run
profiler should somehow cleanup any persisted TopComponent data upon uninstall
Is uninstalling the Profiler really a supported usecase now when the Profiler is a part of standard IDE ditribution?
i would close this issue as invalid since NB profiler is now an integral part of the NB IDE and it's impossible to un-install it from outside of the IDE. when un-installing using the plugins manager all TCs are closed before uninstallation proceeds thus basically eliminating the problem with stalled serialized TCs
Verified