Stack overflow in xul!mozilla_dump_image
Categories
(Core :: Layout, defect)
Tracking
()
People
(Reporter: vulbugs, Unassigned)
References
Details
(Keywords: crash, testcase)
Crash Data
Attachments
(1 file)
455.66 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36
Steps to reproduce:
open the poc.html
70.0b8 (64-bit) windows10
Actual results:
Stack overflow - code c00000fd (first chance)
Expected results:
no crash
Updated•5 years ago
|
Comment 1•5 years ago
|
||
I'm not able to reproduce this with the latest nightly build. There isn't much to go on here.
Comment 2•5 years ago
|
||
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
I can't reproduce this issue on the latest Nightly 72.0a1.
Vulbugs, are you still able to reproduce this issue? If yes, could you please type about:crashes in your address bar and then copy and paste the Report ID for the latest crash? You can find more details about how to do this here:
https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
Thanks!
Comment 4•5 years ago
|
||
I think this is a duplicate of bug 1403656
Updated•5 years ago
|
I think it's been fixed since https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=504f24d7331637bcaea72ff6dcf1ae38588defb5&tochange=0fe71f31e0450543ab885bde8d172e629aec9898 (after Nightly 2019-09-17).
Comment 6•5 years ago
|
||
vulbugs, are you still able to reproduce this issue on Firefox 71? It seems it has fixed in 71 as per comment 5.
Comment 8•5 years ago
|
||
Thanks! So this issue was fixed by either bug 1575964 or bug 1580346. I will close this as a duplicate, but I am not sure which one fixed this. I will bet bug 1580346, Ting-Yu or Mats will correct me If I am wrong.
Comment 9•5 years ago
|
||
I was able to use mozregression to further narrow down the range YF provided in comment 5. I got https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d210f9a51d2104b2a40f17a814a51896fb5b19f8&tochange=0fe71f31e0450543ab885bde8d172e629aec9898 So it was Bug 1575964 that fixed this bug.
Description
•