Comment #20 on issue 25857 by [email protected]: Crash :
-[ChromeEventProcessingWindow shortcircuitEvent:]
http://code.google.com/p/chromium/issues/detail?id=25857
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=30668
------------------------------------------------------------------------
r30668 | [email protected] | 2009-10-31 08:35:26 -0700 (Sat, 31 Oct 2009) |
16 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_mac.h?r1=30668&r2=30667
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_mac.mm?r1=30668&r2=30667
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/browser_window_controller.mm?r1=30668&r2=30667
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_widget_host_view_mac.mm?r1=30668&r2=30667
DeferredAutoreleasePool didn't work on Snow Leopard.
This is a backout of r30647, but also resurrects the change from
http://codereview.chromium.org/341022 to work around the crash that r30647
solved much more elegantly.
We can't really leave things broken on 10.6, though. I killed most of a
perfectly good Friday evening trying to figure out how to salvage r30647,
but the DeferredAutoreleasePool approach seems doomed without making private
calls.
This makes me really sad.
BUG=25857, 26399, 26402
TEST=Does it launch on Snow Leopard now? Does it crash when you close
windows?
Review URL: http://codereview.chromium.org/339095
------------------------------------------------------------------------
--
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
-~----------~----~----~----~------~----~------~--~---
