433666 - Firefox messes up when translating german words with umlauts on "Beolingus" website

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[tobiwei]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14

I have seen the following behavior often, maybe 20 times in the last 3 months but it happens not every time.

Translating a german word with umlauts on this website to english, let firefox crash with the windows "An error has occures" message. >>> http://dict.tu-chemnitz.de/

This happens often if firefox is already used for a few hours and has still some memory in usage and a few tabs are opened. This has been reproduced on 3 different PCs, 2 with WinXP SP2 and 1 with WinVista (without SP1).

Reproducible: Sometimes

Steps to Reproduce:
1. Surf a few hours and let firefox eat your pc memory :-)
2. Go to the mentioned website and translate a german word containing umlauts to english
3. If you're lucky, firefox will crash.

Comment 1

[tobiwei]

I report this Bug with Firefox 2.0.0.14 but it was seen really much before, maybe 2.0.0.9 or earlier... this is not a new bug/behavior.

Comment 2

[tobiwei]

Can you confirm this behavior?

Comment 3

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.