Closed Bug 295195 Opened 19 years ago Closed 19 years ago

Using extension Spellbound 0.7.3 choosing option Recheck Page causes a crash [@ GetScopeOfObject f4e69a55 ]

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: ria.klaassen, Unassigned)

References

Details

(Keywords: crash)

Crash Data

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050522 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050522 Firefox/1.0+

Using extension Spellbound 0.7.3 choosing option Recheck Page causes a crash.

[url=http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=6055582y]Talkback
FastFind - Incident ID: 6055582 [@ GetScopeOfObject] (FirefoxTrunk - 2005052214
- Windows NT 5.1 build 2600)[/url]

See also forum discussion: 
http://forums.mozillazine.org/viewtopic.php?p=1485681#1485681

At least the nightly of 19 May had no crash.

Reproducible: Always

Steps to Reproduce:
1. Install Spellbound 0.7.3 on the latest trunk build
2. Paste some text in the input box of a forum and choose Check Spelling in the
rightclick menu
3. Then choose Recheck

Actual Results:  
A crash.

Expected Results:  
Recheck spelling.
This looks to be related to bug 295215 from the TB
Keywords: crash
Summary: Using extension Spellbound 0.7.3 choosing option Recheck Page causes a crash → Using extension Spellbound 0.7.3 choosing option Recheck Page causes a crash [@ GetScopeOfObject f4e69a55 ]
Probably the same as bug 295101
Depends on: 295101
> 1. Install Spellbound 0.7.3 on the latest trunk build

URL?  Please always provide one when filing a bug that requires a specific
extension.
OK, I think I found this extension (on sourceforge).  If that's the one, this is
fixed by patch in bug 295101.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Crash Signature: [@ GetScopeOfObject f4e69a55 ]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.