Crash in QuickTimeUSBVDCDigitizer
Originator: | sail | ||
Number: | rdar://12231124 | Date Originated: | 9/4/2012 |
Status: | Open | Resolved: | |
Product: | Mac OS X | Product Version: | 10.8.1/12B19 |
Classification: | Hang | Reproducible: | Sometimes |
04-Sep-2012 01:49 PM Sailesh Agrawal: Summary: Google Chrome users are reporting crashes in the com.apple.QuickTimeUSBVDCDigitizer module. Steps to Reproduce: Not clear yet. It seems to be happening on 10.7 and 10.8. Might be related to switch between integrated and discrete graphics cards. See stack trace. Expected Results: No crash Actual Results: Crash. Regression: Not sure. Notes: Crash log attached. See this bug for more info: http://code.google.com/p/chromium/issues/detail?id=139164 Here's the backtrace from the crash: Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread 0 com.apple.QuickTimeUSBVDCDigitizer 0x0d4fa5df 0xd4ec000 + 58847 1 com.apple.QuickTimeUSBVDCDigitizer 0x0d50b45f 0xd4ec000 + 128095 2 com.apple.QuickTimeUSBVDCDigitizer 0x0d50afc9 0xd4ec000 + 126921 3 com.apple.CoreGraphics 0x91189139 CGSReconfigNotifierCalloutListInvokeAll + 53 4 com.apple.CoreGraphics 0x911c877c displayConfigFinalizedProc + 350 5 com.apple.CoreGraphics 0x911c8a39 displayAcceleratorChangedProc + 645 6 com.apple.CoreGraphics 0x90ecd60e CGSPostLocalNotification + 295 7 com.apple.CoreGraphics 0x90f0afa6 notify_datagram_handler + 291 8 com.apple.CoreGraphics 0x90ecaf2b CGSDispatchDatagramsFromStream + 249 9 com.apple.CoreGraphics 0x90ecab23 snarf_events + 428 10 com.apple.CoreGraphics 0x90eca84c CGSGetNextEventRecordInternal + 125 11 com.apple.CoreGraphics 0x90eca784 CGEventCreateNextEvent + 41 12 com.apple.HIToolbox 0x97be3b42 PullEventsFromWindowServerOnConnection(unsigned int, unsigned char) + 81 13 com.apple.CoreFoundation 0x906eb1ef __CFMachPortPerform + 303 14 com.apple.CoreFoundation 0x906eb0a5 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 53 15 com.apple.CoreFoundation 0x906eacd2 __CFRunLoopDoSource1 + 146 16 com.apple.CoreFoundation 0x907209c6 __CFRunLoopRun + 2038 17 com.apple.CoreFoundation 0x9071fd6a CFRunLoopRunSpecific + 378 18 com.apple.CoreFoundation 0x9071fbdb CFRunLoopRunInMode + 123 19 com.apple.HIToolbox 0x97bdc8aa RunCurrentEventLoopInMode + 242 20 com.apple.HIToolbox 0x97bdc619 ReceiveNextEventCommon + 374 21 com.apple.HIToolbox 0x97bdc494 BlockUntilNextEventMatchingListInMode + 88 22 com.apple.AppKit 0x94f19a5a _DPSNextEvent + 724 23 com.apple.AppKit 0x94f1928c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119 24 com.apple.AppKit 0x94f0f6dc -[NSApplication run] + 855 25 com.google.Chrome.framework 0x00da7f81 base::MessagePumpNSApplication::DoRun (message_pump_mac.mm:591) 26 com.google.Chrome.framework 0x00da7abc base::MessagePumpCFRunLoopBase::Run (message_pump_mac.mm:177) 27 com.google.Chrome.framework 0x00dd5380 MessageLoop::RunHandler (message_loop.cc:393) 28 com.google.Chrome.framework 0x00de7af1 base::RunLoop::Run (run_loop.cc:84) 29 com.google.Chrome.framework 0x00326bc0 ChromeBrowserMainParts::MainMessageLoopRun (chrome_browser_main.cc:1963) 30 com.google.Chrome.framework 0x0006c440 content::BrowserMainLoop::RunMainMessageLoopParts (browser_main_loop.cc:451) 31 com.google.Chrome.framework 0x0008f133 (anonymous namespace)::BrowserMainRunnerImpl::Run (scoped_ptr.h:202) 32 com.google.Chrome.framework 0x0006b7a1 BrowserMain (browser_main.cc:21) 33 com.google.Chrome.framework 0x00d4a32b content::ContentMainRunnerImpl::Run (content_main_runner.cc:375) 34 com.google.Chrome.framework 0x00d495d0 content::ContentMain (content_main.cc:35) 35 com.google.Chrome.framework 0x0002c739 ChromeMain (chrome_main.cc:32) 36 com.google.Chrome 0x00026f58 main (chrome_exe_main_mac.cc:20) 37 com.google.Chrome 0x00026f05 0x26000 + 3845 04-Sep-2012 01:49 PM Sailesh Agrawal: 'ChromeCrash.txt' was successfully uploaded
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!