Chromium Code Reviews
DescriptionThere were two leaks detected here.
The first is from a preexisting bug. GpuProcessHost::SendOnIO will leak the message if the IO thread is not present. Note that it will not leak the message if the IO thread is present, but the GPU process is absent.
The second issue is that we would keep around one GpuData-Observer indefinitely. I changed this to be scoped to the task manager.
On the second issue I have a concern here that there may be a race between destruction of the task manager and the GpuDataManager. The TaskManagerModel dtor calls into GpuDataManager::RemoveObserver, but is this safe if the GpuDataManager's dtor has been called first? Do we offer any guarantees of this? In practice, neither singleton's dtor is called when I just run the browser, and the GpuDataManager's dtor is called second in the unit test.
BUG=143563
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=152847
Patch Set 1 #
Total comments: 2
Patch Set 2 : Remove suppressions now that issue 143563 is fixed #
Messages
Total messages: 9 (0 generated)
|
||||||||||||||||||||||||||||