Closed Bug 944181 Opened 12 years ago Closed 24 days ago

"Assertion failure: valid (Should never call with a bogus aCharset.)" in nsScanner::SetDocumentCharset

Categories

(Core :: Networking, defect, P5)

x86_64
macOS
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: assertion, testcase, Whiteboard: [necko-would-take])

Crash Data

Attachments

(2 files)

Attached file testcase
No description provided.
Attached file stack (lldb)
Assertion failure: valid (Should never call with a bogus aCharset.), at parser/htmlparser/src/nsScanner.cpp:123
Crash Signature: [@ nsScanner::SetDocumentCharset(nsACString_internal const&, int) ]
Crash Signature: [@ nsScanner::SetDocumentCharset(nsACString_internal const&, int) ] → [@ nsScanner::SetDocumentCharset(nsACString_internal const&, int) ] [@ nsScanner::SetDocumentCharset ]
Whiteboard: [necko-would-take]
Priority: -- → P5
QA Whiteboard: qa-not-actionable
Severity: critical → S2

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Severity: S2 → S3

The code has changed and the assertion no longer exists.

Status: NEW → RESOLVED
Closed: 24 days ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: