Closed Bug 589040 Opened 14 years ago Closed 14 years ago

crash when replying to or composing an email

Categories

(Firefox :: General, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 588643

People

(Reporter: adriou12, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b5pre) Gecko/20100819 Minefield/4.0b5pre Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b5pre) Gecko/20100819 Minefield/4.0b5pre Minefield first crashed when I tried to reply to an email, in gmail's webmail. I tried every option: clicking on the reply button using keyboard shortcuts clicking in the reply zone I also tried opening a new email, same result. Extremely quick crash. I submitted bug reports for each crash. Here's my list, sorry if it's too long: bp-09fa87da-9db2-4bd3-9d78-140922100819 bp-456cd8fa-e568-4492-8380-e43e02100819 bp-ec2a3475-4864-4327-b69f-a39e52100819 bp-ebcb3483-31c8-4570-a6b6-870a72100819 bp-40a1166c-ab5a-4599-9bb7-2aad12100819 bp-96550cdf-4c60-4447-bba4-d706a2100819 The crash reason seems to always be the same: "EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE" Not all that surprising, really. All the crashes occurred for the same reason. Reproducible: Always Steps to Reproduce: 1. Login to gmail with Minefield 4.0b5pre 2. Try to write an email Actual Results: Minefield crashed. On one occasion it took a little bit more time, but usually it crashed within three seconds. Most of the time the restart was immediate, once Minefield asked whether I wanted to restore my session. Expected Results: No crash. General usage of gmail didn't seem awkward. Might have been a bit sluggish, but I hadn't really noticed.
Tested if it still crashed after latest security fix, problem still there. bp-c9b0f2ad-61ab-4e6e-8c03-df4742100819
One more thing. I tested with and without addons. I didn't try without the plugins, though. And the reason why I'm using the 32 bit version is because I wanted to be able to use the usual plugins. Hope this helps.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.