Closed
Bug 1155872
Opened 10 years ago
Closed 10 years ago
APZ Crashing in platform_memmove
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mchang, Unassigned)
Details
Crash Data
While browsing with e10s on nightly, I'm getting lots of APZ crashes while scrolling. They look like this:
https://crash-stats.mozilla.com/report/index/ba09f98f-9e45-4740-a7f1-98b8a2150417
Comment 1•10 years ago
|
||
Strange. It looks like the crash is coming from the copy constructor of FrameMetrics::mContentDescription when a copy of the FrameMetrics is made by NS_NewRunableMethodWithArg, but I'm not sure why it would be crashing.
Comment 2•10 years ago
|
||
Nothing jumps out at me either here. I noticed that there's pre-existing crashes with this signature on OS X though, so it's probably a pre-existing bug in the string code that's getting hit more often, or something. Maybe related to off-main-thread use of the string classes?
Updated•10 years ago
|
Crash Signature: [@ _platform_memmove$VARIANT$Unknown] → [@ _platform_memmove$VARIANT$Unknown]
[@ _platform_memmove$VARIANT$Ivybridge ]
I confirm on e10s-Nightly on OS X 10.10.4: https://crash-stats.mozilla.com/report/index/dc2a70e5-e31d-4f39-ae96-093582150521
Comment 4•10 years ago
|
||
FWIW, I hit this (bp-276523cb-bfc1-4bbc-a9f1-1f7a12150711) when printing a page on Twitter, in non-E10S mode with a current Nightly.
Comment 5•10 years ago
|
||
(In reply to Justin Dolske [:Dolske] from comment #4)
> FWIW, I hit this (bp-276523cb-bfc1-4bbc-a9f1-1f7a12150711) when printing a
> page on Twitter, in non-E10S mode with a current Nightly.
This one looks unrelated to APZ, so I filed 1182732 about it.
I've been using APZ in my main browser for three days now and haven't hit this crash again, so I think it got fixed, or at least hidden. I was hitting it all the time a few weeks ago when I last tried APZ in my main profile.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•