Firefox crashes when interacting with specific page: assertion failed: mem::size_of::<T>() <= slice.len()
Categories
(Core :: Graphics, defect, P1)
Tracking
()
People
(Reporter: danburzo, Assigned: tnikkel)
References
(Regression, )
Details
(Keywords: regression)
Crash Data
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/109.0
Steps to reproduce:
Scroll around the web page: https://work.nicochilla.com/tractatus-tree/dendrogram.html
Actual results:
Firefox crashes.
Application Basics
Name: Firefox
Version: 109.0
Build ID: 20230112150232
Distribution ID:
Update Channel: release
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/109.0
OS: Darwin 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11 02:04:44 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8103
Rosetta Translated: false
Multiprocess Windows: 1/1
Fission Windows: 1/1 Enabled by default
Remote Processes: 8
Enterprise Policies: Inactive
Google Location Service Key: Found
Google Safebrowsing Key: Found
Mozilla Location Service Key: Found
Safe Mode: false
Memory Size (RAM): 16.0 GB
Disk Space Available: 8.0 GB
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
Kash reproduced and here is his crash => https://crash-stats.mozilla.org/report/index/7eee3edf-8862-45bd-b718-814250230224
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Easy to reproduce, all you have to do is scroll down (perhaps rapidly).
Assignee | ||
Comment 4•2 years ago
|
||
Seems like the browser width is important in reproducing. I think I can reproduc consistently enough (and test each build enough to be sure) to regression range it to this
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=ca774a5b6b7b6874f91abb76a422582d37169a57&tochange=5c87b1e70b4401f9282c5649c32d1953a8c9e9cc
I think that would be bug 1753404
Also pretty sure I reproduced this on Windows as well.
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Set release status flags based on info from the regressing bug 1753404
:nical, since you are the author of the regressor, bug 1753404, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 6•2 years ago
|
||
Set release status flags based on info from the regressing bug 1753404
Updated•2 years ago
|
![]() |
||
Updated•2 years ago
|
Comment 7•2 years ago
|
||
:nical is this still on the radar for a possible uplift to a 112 dot release?
Updated•2 years ago
|
Comment 8•2 years ago
•
|
||
:nical is this still on the radar for a possible uplift to a 112 dot release?
Just coming back from parental leave. No and probably not for a few other releases since the problem isn't well understood.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 9•1 year ago
|
||
Dan, is this crash still happening for you with the current Nightly build (Fx120)?
Reporter | ||
Comment 10•1 year ago
|
||
Bob, I am still able to cause a crash in Firefox 120.0a1 Nightly through sustained, frenetic interaction with the page.
Comment 11•1 year ago
|
||
Thanks, Dan. Can you please attach a full and recent about:support
dump to this report?
Updated•1 year ago
|
Comment 12•1 year ago
|
||
easy enough to repro on my Win11 machine - just zoom in to 240% and then grab the scroll-bar and drag it down to scroll.
Comment 13•1 year ago
|
||
"nical is the closest we have to a Blob owner, and it does repro for @gw, so hopefully tractable."
Reporter | ||
Comment 14•11 months ago
|
||
(Sorry, there seems to be an awful lot of info in that dump, I’d rather not attach it all publicly. If I understand correctly, the team is able to reproduce the issue.)
Updated•10 months ago
|
Assignee | ||
Comment 15•9 months ago
|
||
I've been debugging the fuzz bug 1805333 for the same assert (because it is reduced and easy to work with). I think it will probably turn out to be the same issue.
Updated•8 months ago
|
Comment 16•7 months ago
|
||
Setting to P1 so it appears on my internal tracking radar.
Updated•10 days ago
|
Description
•