Comment #44 on issue 2 by [email protected]: Testing if chromium id  
works
http://code.google.com/p/chromium/issues/detail?id=2

The following revision refers to this bug:
     http://src.chromium.org/viewvc/chrome?view=rev&revision=30647

------------------------------------------------------------------------
r30647 | [email protected] | 2009-10-30 16:05:27 -0700 (Fri, 30 Oct  
2009) | 13 lines
Changed paths:
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_mac.h?r1=30647&r2=30646
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_mac.mm?r1=30647&r2=30646
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/browser_window_controller.mm?r1=30647&r2=30646
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_widget_host_view_mac.mm?r1=30647&r2=30646

Cleans up our autorelease handling so that we don't create a layered
autorelease pool in our run loop source if there is one already on the stack
above us. This allows Cocoa to clean up all the objects at the same time as  
it
expects to do. There may be more "interesting" code that can be removed now
that this is in. Initially we were going to implement it by checking the
nesting levels of the runloops, but it turns out by the time sendEvent is
called at the upper level we are already out of the "CFRunloopRun" call so
our nesting count isn't a valid indicator of our state.

TEST=1) See bug 25857. 2) Start up. Open 3+ windows. Quit.
BUG=25857

Review URL: http://codereview.chromium.org/343024
------------------------------------------------------------------------


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to