Community
Participate
Working Groups
Build ID: M20090211-1700 Steps To Reproduce: Using test case PerformanceExample in TPTP test suites. 1. Profile Configuration: Select "Memory Analysis" with "Track object allocation sites" option checked. In Java Profiling Options, uncheck "Automatically determine filtering criteria" option and add java.awt.* INCLUDE, PerformanceExample INCLUDE into filter list. 2. Start profiling and open "Object Allocation" view. 3. You can see two "Button" objects are allocated bot in "Memory Statistics" and "Allocation Details" (They are Add and Remove buttons in PerformanceExample App). 4. Click "Add" in PerformanceExample and Refresh profiling session in Eclipse workbench. You will find that three Button objects shown in "Allocation Details" while only old two of them are shown in "Memory Statistics" view. More information: This bug is found when I investigate bug 282952. The problem can be reproduced with TPTP-4.5.2.1-200907211032 build on WindowsXP.
The Object Allocation tab is not hooked with the refreshed button I believe. If you switch to the memory statistic tab and double click the object to open the detail in allocation tab should workaround the problem for now.
(In reply to comment #1) > The Object Allocation tab is not hooked with the refreshed button I believe. If > you switch to the memory statistic tab and double click the object to open the > detail in allocation tab should workaround the problem for now. > Yes. If navigate from memory statistic tab to allocation details tab by double click, the correct information is shown in allocation details view. It seems the objects info is only updated in allocation details view.
*** Bug 288187 has been marked as a duplicate of this bug. ***
Re-targeting to TPTP 4.6.2.
The memory statistics is refreshed upon clicking on the Refresh view button in Profiling monitor view and I cannot reproduce the problem. I double checked the code and the update in BaseMemoryStatisticView is called upon Refresh event is fired. Thread [main] (Suspended (breakpoint at line 376 in BaseMemoryStatisticView)) BaseMemoryStatisticView.update() line: 376 MemoryAnalysisPage.refreshPage() line: 47 MemoryAnalysisViewer(TraceViewer).refreshPage(Object) line: 428 MemoryAnalysisViewer(TraceViewer).handleProfileEvent(ProfileEvent) line: 579 TraceUIManager$1.run() line: 168 UISynchronizer(Synchronizer).syncExec(Runnable) line: 179 UISynchronizer.syncExec(Runnable) line: 150 Display.syncExec(Runnable) line: 4329 TraceUIManager.notifyProfileEventListener(ProfileEvent) line: 161 UIPlugin.notifyProfileEventListener(ProfileEvent) line: 602 ResourceItemControlProvider$1RefreshView.run() line: 129 ResourceItemControlProvider$1RefreshView(Action).runWithEvent(Event) line: 498 ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584 ActionContributionItem.access$2(ActionContributionItem, Event, boolean) line: 501 ActionContributionItem$6.handleEvent(Event) line: 452 EventTable.sendEvent(Event) line: 84
This defect had been resolved as WORKSFORME for more than 1 month. Closing this on the reporter's behalf. Please verify with the latest TPTP 4.7.2 driver and re-open if this is still a problem. TPTP 4.7.2 driver can be downloaded from: http://www.eclipse.org/tptp/home/downloads/?ver=4.7.2
Closing in TPTP 4.7.2 release.
