Closed
Bug 764336
Opened 13 years ago
Closed 13 years ago
crash in nsCSSRendering::PaintGradient
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: tessarakt, Unassigned)
Details
(Keywords: crash)
Crash Data
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20100101 Firefox/14.0
Build ID: 20120605113340
Steps to reproduce:
I just used Firefox normally.
Actual results:
Firefox crashed with signature [@ je_free | nsCSSRendering::PaintGradient(nsPresContext*, nsRenderingContext&, nsStyleGradient*, nsRect const&, nsRect const&, nsRect const&) ], see https://crash-stats.mozilla.com/report/index/bp-2e1f367e-b88d-40eb-930b-0f1ad2120612
Comment 1•13 years ago
|
||
There are 6 crashes across all versions over the last four weeks.
https://crash-stats.mozilla.com/report/list?signature=je_free+|+nsCSSRendering%3A%3APaintGradient%28nsPresContext*%2C+nsRenderingContext%26%2C+nsStyleGradient*%2C+nsRect+const%26%2C+nsRect+const%26%2C+nsRect+const%26%29
Does it happen in Safe Mode (see http://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode)? If no, which extension causes your problem?
Severity: normal → critical
Crash Signature: [@ je_free | nsCSSRendering::PaintGradient(nsPresContext*, nsRenderingContext&, nsStyleGradient*, nsRect const&, nsRect const&, nsRect const&) ]
Component: Untriaged → Style System (CSS)
Keywords: crash
Product: Firefox → Core
QA Contact: untriaged → style-system
Summary: Firefox crashes [@ je_free | nsCSSRendering::PaintGradient(nsPresContext*, nsRenderingContext&, nsStyleGradient*, nsRect const&, nsRect const&, nsRect const&) ] → crash in nsCSSRendering::PaintGradient
| Reporter | ||
Comment 2•13 years ago
|
||
Umm, sorry for the hazzle. Our sysadmin changed my RAM without notifying me, and the new module was apparently broken. This explains seemingly unconnected crashes with increased frequency ...
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•