Closed Bug 1059762 Opened 12 years ago Closed 12 years ago

Click dragging a loaded GMail tab causes Firefox to crash @ OOM | small

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1053934

People

(Reporter: ahal, Unassigned)

Details

(Keywords: crash)

Link to crash report: https://crash-stats.mozilla.com/report/index/25a9246e-177b-43af-930d-93ba52140828 Reproducible: Always This doesn't seem to happen with other websites I tested, though the crash report seems to suggest an OOM situation. Please move to the proper component if this is not it.
In case it isn't clear from the summary.. STR: 1) Open gmail and wait for it to finish loading 2) Click and drag it to a new position on the tab bar 3) Crash
It seems trying to create the canvas stuff for the preview image we show while dragging tabs is crashing in graphics-land. Moving to Core::Graphics... Is this a recent regression?
Component: Tabbed Browser → Graphics
Flags: needinfo?(ahalberstadt)
Keywords: crash
Product: Firefox → Core
I believe so. I just noticed it today, and I usually have a gmail tab open, so I think I would have noticed before now if it was a long running issue.
Flags: needinfo?(ahalberstadt)
(In reply to Andrew Halberstadt [:ahal] from comment #3) > I believe so. I just noticed it today, and I usually have a gmail tab open, > so I think I would have noticed before now if it was a long running issue. Could you try using mozregression to find a regression window? ( http://mozilla.github.io/mozregression/ ) That'll usually help figure out what's wrong quickest. :-)
The nightly pushlog was: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=daa84204a11a&tochange=dc352a7bf234 The inbound pushlog was: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=daa84204a11a&tochange=78a46df3e3bd which.. um, seems unlikely :). Every inbound bisection was bad, I wonder if there's a bug in mozregression somewhere.
(In reply to Andrew Halberstadt [:ahal] from comment #5) > which.. um, seems unlikely :). Every inbound bisection was bad, I wonder if > there's a bug in mozregression somewhere. You know, I ran into that the other day as well. I'll file a bug.
Please reopne if this happens again but otherwise this is probably another dupe of bug 1053934.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Crash Signature: OOM | small
You need to log in before you can comment on or make changes to this bug.