Browser crashes when drag n drop file from file window
Reported by
lisongli...@gmail.com,
Jan 23 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: 1. Open 'http://www.dropzonejs.com/' 2. Click 'Drop files here or click to upload.' and file window shows up 3. Drag files to drop zone. 4. Choose another files in file window and click 'Open' button What is the expected behavior? All the files should appear in drop zone What went wrong? Chrome is stuck Did this work before? N/A Chrome version: 55.0.2883.95 Channel: stable OS Version: OS X 10.12.1 Flash Version: Shockwave Flash 24.0 r0
,
Jan 23 2017
My bad... This issue didn't happen on my Mac, but my colleague's Windows machine. Please check my attachment for detail. In addition, you steps is right to reproduce the issue. In my testing, I can reproduce it 8 time in 10 attempts. Thanks!
,
Jan 30 2017
Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 7 2017
I couldn't reproduce the crash on Windows. Can you provide a crash ID? https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug
,
Feb 7 2017
,
Feb 9 2017
This issue can also be reproduced in most sites that support "browses file" and "drag-n-drop" to upload. Chrome version: 56.0.2924.76 Platform: Windows 10 1. Open any site like https://blueimp.github.io/jQuery-File-Upload/ 2. Click "Add files..." 3. Inside the file browser, drag-n-drop any file from the file browser window to the attachment area 4. Press cancel from the file browser 5. If not crash, repeat 2-3 times 6. The whole Chrome will crash I have tried on my own site and the problem also occurs, on my own site the JavaScript listens to "dragover", "dragleave" and "drop" event. Not sure if this helps but worth mentioning. I have tried to locate the crash report but no luck. It is not filed in Chrome I think.
,
Feb 13 2017
The crash ID is: b312eaf7-8c47-47e0-b649-e9879349e4ba
,
Feb 14 2017
#9, would you tell us Server ID of the crash please?
,
Feb 14 2017
How can I find the server ID?
,
Feb 14 2017
#11, it should be shown in chrome://crashes like: Crash ID b312eaf7-8c47-47e0-b649-e9879349e4ba (Server ID: NNNNNNNNN)
,
Feb 22 2017
Thank you for providing more feedback. Adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 3 2017
Unfortunately no one in Google could reproduce this issue, and crash IDs were not provided. We can't investigate this. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by durga.behera@chromium.org
, Jan 23 2017Labels: M-55 Needs-Feedback