New issue
Advanced search Search tips

Issue 637424 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Crash when pressing Cmd+W during drag-and-drop

Reported by joliss42@gmail.com, Aug 12 2016

Issue description

Chrome Version       : 52.0.2743.116, 54.0.2827.0 canary
OS Version: OS X 10.11.6

What steps will reproduce the problem?
1. Create an empty file test.txt.
2. Open the containing folder in Finder.
3. Open Chrome with an empty tab.
4. Click into Finder so the Finder window has focus.
5. Drag the test.txt file from the Finder over the empty Chrome tab, but don't release.
6. Wait about a second until the Chrome window automatically gains focus during the drag-and-drop operation.
7. While still holding down the mouse button over the Chrome window, press Cmd+W.

Chrome crashes.

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
 
Labels: Needs-Feedback
I wasn't able to reproduce this. Can you visit chrome://crashes and include the crashes from there in this report?

If there's nothing there, open a terminal, and type in the command 
"""
open ~/Library/Application\ Support/Google/Chrome/Crashpad/completed/
""" 
Are there any files there? If so, can you upload the zipped directory?

Comment 2 by joliss42@gmail.com, Aug 15 2016

Sure, crash dump is attached!
ed16d05e-d07b-44f0-b951-c0884d6ae53c.dmp
540 KB Download
Cc: a...@chromium.org
Labels: -Pri-3 -Needs-Feedback Hotlist-Sierra Pri-1
Owner: erikc...@chromium.org
Status: Assigned (was: Unconfirmed)
"""
Thread 0 ( * CRASHED * EXC_BAD_ACCESS / EXC_I386_GPFLT @ 0x108bee5b5 )
0	 [Google Chrome Framework	 -	 web_drag_dest_mac.mm:197] -[WebDragDest draggingUpdated:view:]
1	 [AppKit	 -	 0x5b29f7] -[NSDragDestination _draggingUpdate]
2	 [AppKit	 -	 0x30732f] __42-[NSDragDestination _startDraggingUpdates]_block_invoke
3	 [CoreFoundation	 -	 0x92b94] __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
4	 [CoreFoundation	 -	 0x92823] __CFRunLoopDoTimer
5	 [CoreFoundation	 -	 0x9237a] __CFRunLoopDoTimers
6	 [CoreFoundation	 -	 0x89871] __CFRunLoopRun
7	 [CoreFoundation	 -	 0x88ed8] CFRunLoopRunSpecific
8	 [HIToolbox	 -	 0x30935] RunCurrentEventLoopInMode
9	 [HIToolbox	 -	 0x30677] ReceiveNextEventCommon
10	 [HIToolbox	 -	 0x305af] _BlockUntilNextEventMatchingListInModeWithFilter
11	 [AppKit	 -	 0x48df6] _DPSNextEvent
12	 [AppKit	 -	 0x48226] -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
13	 [AppKit	 -	 0x3cd80] -[NSApplication run]
14	 [Google Chrome Framework	 -	 message_pump_mac.mm:682] base::MessagePumpNSApplication::DoRun(base::MessagePump::Delegate*)
15	 [Google Chrome Framework	 -	 message_pump_mac.mm:246] base::MessagePumpCFRunLoopBase::Run(base::MessagePump::Delegate*)
16	 [Google Chrome Framework	 -	 run_loop.cc:36] base::RunLoop::Run()
17	 [Google Chrome Framework	 -	 chrome_browser_main.cc:2110] ChromeBrowserMainParts::MainMessageLoopRun(int*)
18	 [Google Chrome Framework	 -	 browser_main_loop.cc:961] content::BrowserMainLoop::RunMainMessageLoopParts()
19	 [Google Chrome Framework	 -	 memory:2752] content::BrowserMainRunnerImpl::Run()
20	 [Google Chrome Framework	 -	 browser_main.cc:46] content::BrowserMain(content::MainFunctionParams const&)
21	 [Google Chrome Framework	 -	 content_main_runner.cc:785] content::ContentMainRunnerImpl::Run()
22	 [Google Chrome Framework	 -	 content_main.cc:20] content::ContentMain(content::ContentMainParams const&)
23	 [Google Chrome Framework	 -	 chrome_main.cc:85] ChromeMain
24	 [Google Chrome Canary	 +	 0xd4a]
25	 [Google Chrome Canary	 +	 0xb34]
"""
symbolized_crash.txt
29.9 KB View Download
Labels: -Hotlist-Sierra
Whoops, the bug is on 10.11, not Sierra.

I haven't been able to repro on either OS. The draggingUpdated: callback doesn't seem to arrive until after I let go of the mouse. That seems...odd.

Sign in to add a comment