Immediate crash when selecting special PNG bomb image
Reported by
kristopo...@gmail.com,
Apr 21 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Steps to reproduce the problem: 1. Download the PNG bomb provided at https://github.com/ptrofimov/png-bomb-protection (see attached for a compressed version) 2. Attempt to provide the decompressed PNG file by clicking on it through the file selection dialog of an <input type=file /> interface 3. After selecting the file, the browser crashes immediately with an out of memory error (my desktop I tested it on has 32 GB) What is the expected behavior? Although this may be a malformed image (image magick's identify says it exceeds the user limit), firefox's network tab claims it's a 225,000 by 225,000 transparent image (it will peg the processor here ... but that's there bug), an immediate crash is likely not the most graceful way of handling it. There are many acceptable solutions: 1. A dialog could inform the user that the image is too large. 2. A different dialog could inform the user that the image may be corrupt and can't be used 3. The user's actions could be accommodated, likely against the best interest of the website in question which may also fall victim to the faulty image and the file could be transferred regardless. What went wrong? Chrome crashes immediately with an out of memory error. This could arguably be a bug of the file selection dialog. I don't know the codebase enough to claim culpability Crashed report ID: no How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? No Chrome version: <Copy from: 'about:version'> Channel: n/a OS Version: buster Flash Version: Shockwave Flash 24.0 r0 This is my first time filing a bug here. Please excuse me if I missed any protocol. Thanks!
,
Apr 23 2018
Thanks for filing the issue! its look like out of memory issue.Could you please create new profile without extensions and apps.Re-check once in latest chrome builds(Stable / Canary) and let us know the observations and please provide the crash id from chrome://crashes of the issue which would help us to triage the issue further. Thanks in Advance.
,
Apr 24 2018
Alright thanks. I don't know if I'll have the time to do that in the near term. It's likely a fairly low-priority issue.
,
Apr 24 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 9 2018
kristopolous@ As per comment #3, shall we close this issue.
,
May 9 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 11 2018
Adding Need-Feedback label as per comment #5. @kristopolous: Could you please confirm
,
Nov 9
***Mass UI Triage*** Archiving old bugs. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by kristopo...@gmail.com
, Apr 21 20181.4 KB
1.4 KB View Download