Community
Participate
Working Groups
In the profile configurations dialog, all launch entries now seem to share a global profile setting (e.g. execution analysis, memory analysis), such that changing one seems to affect all the others. To Reproduce: 1. In the profile configurations dialog create two launch entries (any launch type will do, for example Java Application/Eclipse Application, etc). One will be used for Execution profiling, the other should be Memory profiling. 2. On the first launch entry, and set the profiling type to 'Execution Analysis'. Click Apply. 3. Move to the second launch entry, and set the profiling type to 'Memory Analysis'. Click Apply. 4. Move back to the first launch entry, and see that it has changed to 'Memory Analysis'. As it stands the launch types seem to share a global property, which was not previously the case.
I've gone through and tested the previous releases: it works as expected in 4.6.2, does not work in 4.7.0. I've compared the source changes made between the two releases, and my guess at the culprit is bug 313437 (or maybe bug 299294). Mike, can you take a look?
Indeed looks like bug 313437 is the culprit. Seems to be fixed by explicitly calling initializeAfterFetch() from lazyUpdateDataCollectors() in the case where the host and port are identical. This has the effect of skipping the data collector fetch (which is what fixed the accessibility bug) but still performing the 'after fetch' logic, which initializes the data collector tree from the launch config. I'll do some more testing to try and confirm this does not introduce any new wackiness.
Since this is a regression from 4.6.2, let's try to get this into 4.7.2.
Created attachment 186512 [details] Patch Attaching patch. I did some further testing, things look good. Also confirmed this does not regress the accessibility bug.
Jon, could you review the attached patch for 4.7.2?
Patch is good.
Project approved for 4.7.2. Please update the copyright year to 2011 before checking in.
Checked into HEAD.
Closing.
