Issue metadata
Sign in to add a comment
|
Hang in blink::ThemePainterMac::PaintCheckbox in Chrome 67 |
||||||||||||||||||||||
Issue description
Chrome Version: 67.0.3396.99
OS: Mac OS X 10.13.3 (17D47)
What steps will reproduce the problem?
(1) Browse various web sites (not sure Mac model – can follow up)
What is the expected result?
No hangs.
What happens instead?
Chrome hangs frequently – my colleague reports up to 30 times a day. Symbolized sample of the hung renderer process is attached; stack trace excerpt follows. This is clearly the same issue as Issue 844660 and probably the same as Issue 760078, which are crashes rather than renderer hangs. Issue 844660's fix was merged to M68, but not clear why it was not merged to M67. (Did Sandbox v2 not ship in that release?) Regardless, this is affecting some number of users of M67 and should be investigated ASAP.
+ 7440 blink::BoxPainter::PaintBoxDecorationBackground(blink::PaintInfo const&, blink::LayoutPoint const&) (in Google Chrome Framework) load address 0x107580000 + 0x57676cd [optional.h:62]
+ 7440 blink::BoxPainter::PaintBoxDecorationBackgroundWithRect(blink::PaintInfo const&, blink::LayoutPoint const&, blink::LayoutRect const&) (in Google Chrome Framework) load address 0x107580000 + 0x5767c4e [box_painter.cc:183]
+ 7440 blink::ThemePainterMac::PaintCheckbox(blink::Node const*, blink::Document const&, blink::ComputedStyle const&, blink::PaintInfo const&, blink::IntRect const&) (in Google Chrome Framework) load address 0x107580000 + 0x57f3e6d [theme_painter_mac.mm:647]
+ 7440 -[NSButtonCell drawWithFrame:inView:] (in AppKit) + 481 [0x7fff51a478fc]
+ 7440 -[NSButtonCell drawInteriorWithFrame:inView:] (in AppKit) + 1627 [0x7fff51a48836]
+ 7440 -[NSButtonCell imageRectForBounds:] (in AppKit) + 114 [0x7fff519bee6f]
+ 7440 -[NSButtonCell _imageRect:titleRect:forBounds:] (in AppKit) + 278 [0x7fff51d6f71e]
+ 7440 -[NSButtonCell(NSButtonCellPrivate) _imageRectWithRect:] (in AppKit) + 244 [0x7fff519982e8]
+ 7440 NSCellImageRectWithSize_centeredInRect_scaling_flipped (in AppKit) + 56 [0x7fff51984783]
+ 7440 -[NSView _primitiveConvertSizeToBacking:useIntegralizationSpace:] (in AppKit) + 63 [0x7fff5197947f]
+ 7440 -[NSView _transformToBackingUsingIntegralizationSpace:] (in AppKit) + 242 [0x7fff5193f1af]
+ 7440 +[_NSScreenConfiguration latestGreatestBackingScaleFactor] (in AppKit) + 128 [0x7fff522e3b96]
+ 7440 dispatch_once_f (in libdispatch.dylib) + 41 [0x7fff7bc08d03]
+ 7440 _dispatch_client_callout (in libdispatch.dylib) + 8 [0x7fff7bc08d50]
+ 7440 ___NSScreenConfigurationEnsureInitialUpdateOccurred_block_invoke (in AppKit) + 137 [0x7fff522e3c21]
+ 7440 _NSScreenConfigurationUpdateSharedInfoForReason (in AppKit) + 1546 [0x7fff522e427f]
+ 7440 MenuBarInstance::GetAggregateUIMode(unsigned int*, unsigned int*) (in HIToolbox) + 83 [0x7fff536013cf]
+ 7440 GetModeAndOptionsForProcess(__LSASN const*, unsigned int*, unsigned int*) (in HIToolbox) + 63 [0x7fff5360146b]
+ 7440 _LSCopyApplicationInformation (in LaunchServices) + 283 [0x7fff55784f4a]
+ 7440 LSSharedMemoryPage::CopyForSessionID(LSSessionID, bool) (in LaunchServices) + 205 [0x7fff55783b47]
+ 7440 LSClientToServerConnection::LSClientToServerConnection(int, __CFDictionary const*) (in LaunchServices) + 120 [0x7fff558adc28]
+ 7440 LSClientToServerConnection::setupServerConnection(int, __CFDictionary const*) (in LaunchServices) + 847 [0x7fff55781875]
+ 7440 xpc_connection_send_message_with_reply_sync (in libxpc.dylib) + 164 [0x7fff7bf09433]
+ 7440 dispatch_mach_send_with_result_and_wait_for_reply (in libdispatch.dylib) + 53 [0x7fff7bc23fa1]
+ 7440 _dispatch_mach_send_and_wait_for_reply (in libdispatch.dylib) + 756 [0x7fff7bc23ab6]
+ 7440 mach_msg (in libsystem_kernel.dylib) + 60 [0x7fff7bd87cdc]
+ 7440 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x7fff7bd887c2]
,
Aug 6
Note, I just realized my colleague experiencing this issue should have received the Chrome 68 update by now. Will make sure that update's taken and that it addresses the problem.
,
Aug 6
My colleague's installed the Chrome 68 update and indicates that there haven't been any issues since. Going to close this as WontFix, though perhaps the original fix for Issue 844660 should have been merged to M67.
,
Aug 13
We didn't merge the fix to M67 because this only occurs with a Finch experiment that was at 10% on stable. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by chrishtr@chromium.org
, Aug 6