Firefox 6.0a1 Crash Report [@ IsBreakElement ]

RESOLVED FIXED in mozilla6

Status

()

Core
Spelling checker
--
critical
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: marcia, Assigned: Ehsan)

Tracking

({crash, regression, reproducible})

Trunk
mozilla6
crash, regression, reproducible
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

6 years ago
This bug was filed from the Socorro interface and is 
report bp-754bc3cc-0c40-4060-b2ee-eea172110425 .
============================================================= 

Seen while reviewing trunk crash stats. https://crash-stats.mozilla.com/report/index/754bc3cc-0c40-4060-b2ee-eea172110425 is one report.

Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 	xul.dll 	IsBreakElement 	extensions/spellcheck/src/mozInlineSpellWordUtil.cpp:507
1 	xul.dll 	mozInlineSpellWordUtil::BuildSoftText 	extensions/spellcheck/src/mozInlineSpellWordUtil.cpp:569
(Reporter)

Updated

6 years ago
Component: General → Spelling checker
Product: Firefox → Core
QA Contact: general → spelling-checker
(Reporter)

Comment 1

6 years ago
http://tinyurl.com/4xu9xcj links to the most recent crashes. This crash happens on Windows, Mac and Linux.
OS: Windows NT → All
Hardware: x86 → All
(Reporter)

Updated

6 years ago
Duplicate of this bug: 652481
I managed to reproduce this when playing with Yandex search...
Assignee: nobody → ehsan
STR:

1. Search for something on Yandex.
2. on the results page, right click the search field, and check the Check Spelling menu item.
3. Edit the search query to make it incorrect as far as spelling is concerned.
4. Press back.  -> Crash.
Blocks: 616684
Keywords: regression
(Reporter)

Updated

6 years ago
Keywords: reproducible
Fixed by backout of bug 616684.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Keywords: reproducible
Resolution: --- → FIXED
Keywords: reproducible
Target Milestone: --- → mozilla6

Updated

6 years ago
Duplicate of this bug: 652763
Crash Signature: [@ IsBreakElement ]
You need to log in before you can comment on or make changes to this bug.