Unexpected errors while accessing google maps in chrome
Reported by
register...@gmail.com,
Mar 14 2016
|
||||||
Issue descriptionChrome Version : Google Chrome Version 48.0.2564.116 (64-bit) URLs (if applicable) : https://google-developers.appspot.com/maps/documentation/javascript/examples/full/map-simple OS version : 10.11 Behavior in Safari 3.x/4.x (if applicable): N.A. Behavior in Firefox 3.x (if applicable): N.A. Behavior in Chrome for Windows: N.A. What steps will reproduce the problem? (1) open chrome from terminal /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging --v=1 (2) visit https://google-developers.appspot.com/maps/documentation/javascript/examples/full/map-simple (3) see output log in terminal What is the expected result? Ideally there shouldn't be an error. What happens instead? 2016-03-14 20:02:21.219 Google Chrome[51785:5374918] Inconsistent set of values to create NSBitmapImageRep 2016-03-14 20:02:21.219 Google Chrome[51785:5374918] It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil. This is a programming error. Break on void _NSWarnForDrawingImageWithNoCurrentContext() to debug. This will be logged only once. This may break in the future. 2016-03-14 20:02:21.219 Google Chrome[51785:5374918] Inconsistent set of values to create NSBitmapImageRep
,
Mar 15 2016
I was able to reproduce this bug. I followed the instructions and added a breakpoint. It's not immediately clear why this error is being emitted, nor the source of the problem.
"""
* thread #1: tid = 0x11d96c5, 0x00007fff99e02a95 AppKit`_NSWarnForDrawingImageWithNoCurrentContext, name = 'CrBrowserMain', queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
* frame #0: 0x00007fff99e02a95 AppKit`_NSWarnForDrawingImageWithNoCurrentContext
frame #1: 0x00007fff999c47b8 AppKit`-[NSImage drawInRect:fromRect:operation:fraction:] + 97
frame #2: 0x00007fff99d371b6 AppKit`-[NSCursor _premultipliedARGBBitmaps] + 1354
frame #3: 0x00007fff9995520e AppKit`-[NSCursor _reallySet] + 175
frame #4: 0x00007fff999550fe AppKit`-[NSCursor set] + 219
frame #5: 0x00007fff99973d7a AppKit`-[NSWindow(NSCarbonExtensions) _setCursorForMouseLocation:] + 412
frame #6: 0x00007fff9a036dd2 AppKit`___NSWindowGetDisplayCycleObserver_block_invoke6378 + 1571
frame #7: 0x00007fff99c7d2cd AppKit`__37+[NSDisplayCycle currentDisplayCycle]_block_invoke19 + 292
frame #8: 0x00007fff87853b5d QuartzCore`CA::Transaction::run_commit_handlers(CATransactionPhase) + 85
frame #9: 0x00007fff876edddf QuartzCore`CA::Context::commit_transaction(CA::Transaction*) + 515
frame #10: 0x00007fff876eda24 QuartzCore`CA::Transaction::commit() + 508
frame #11: 0x00007fff876fc917 QuartzCore`CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) + 71
frame #12: 0x00007fff9d22de37 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
frame #13: 0x00007fff9d22dda7 CoreFoundation`__CFRunLoopDoObservers + 391
frame #14: 0x00007fff9d21f358 CoreFoundation`CFRunLoopRunSpecific + 328
frame #15: 0x00007fff9ba89935 HIToolbox`RunCurrentEventLoopInMode + 235
frame #16: 0x00007fff9ba8976f HIToolbox`ReceiveNextEventCommon + 432
frame #17: 0x00007fff9ba895af HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 71
frame #18: 0x00007fff998b70ee AppKit`_DPSNextEvent + 1067
frame #19: 0x00007fff99c83943 AppKit`-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
frame #20: 0x00007fff998acfc8 AppKit`-[NSApplication run] + 682
frame #21: 0x000000011267af22 libbase.dylib`base::MessagePumpNSApplication::DoRun(this=0x0000000100113ba0, delegate=0x000000010010cfe0) + 306 at message_pump_mac.mm:665
frame #22: 0x000000011267981d libbase.dylib`base::MessagePumpCFRunLoopBase::Run(this=0x0000000100113ba0, delegate=0x000000010010cfe0) + 125 at message_pump_mac.mm:238
frame #23: 0x00000001127a5303 libbase.dylib`base::MessageLoop::RunHandler(this=0x000000010010cfe0) + 275 at message_loop.cc:440
frame #24: 0x0000000112838725 libbase.dylib`base::RunLoop::Run(this=0x00007fff5fbfeaa8) + 85 at run_loop.cc:35
frame #25: 0x0000000102349b10 libchrome_main_dll.dylib`ChromeBrowserMainParts::MainMessageLoopRun(this=0x0000000134f04600, result_code=0x0000000134f04488) + 400 at chrome_browser_main.cc:1817
frame #26: 0x0000000116b86947 libcontent.dylib`content::BrowserMainLoop::RunMainMessageLoopParts(this=0x0000000134f04470) + 359 at browser_main_loop.cc:947
frame #27: 0x0000000116b94ecf libcontent.dylib`content::BrowserMainRunnerImpl::Run(this=0x0000000134f041a0) + 447 at browser_main_runner.cc:152
frame #28: 0x0000000116b7e24c libcontent.dylib`content::BrowserMain(parameters=0x00007fff5fbff298) + 348 at browser_main.cc:44
frame #29: 0x00000001168748e7 libcontent.dylib`content::RunNamedProcessTypeMain(process_type="", main_function_params=0x00007fff5fbff298, delegate=0x00007fff5fbff5f0) + 599 at content_main_runner.cc:395
frame #30: 0x0000000116876681 libcontent.dylib`content::ContentMainRunnerImpl::Run(this=0x0000000134e127f0) + 577 at content_main_runner.cc:766
frame #31: 0x0000000116873b30 libcontent.dylib`content::ContentMain(params=0x00007fff5fbff5d0) + 144 at content_main.cc:19
frame #32: 0x0000000102004dd3 libchrome_main_dll.dylib`::ChromeMain(argc=4, argv=0x00007fff5fbff748) + 83 at chrome_main.cc:84
frame #33: 0x000000010000101f Chromium`main(argc=4, argv=0x00007fff5fbff748) + 783 at chrome_exe_main_mac.c:87
frame #34: 0x0000000100000d04 Chromium`start + 52
"""
,
Mar 15 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 20 2017
,
Apr 16 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 16 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by meh...@chromium.org
, Mar 14 2016