284493 - firefox crashes when making changes to sprintpcs.com pcs mail address book

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[A. Sapuntzakis]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

First time that it crashed, I was able to do a fair amount of editing of my 
sprinpcs pcs mail (online) address book. Now, it seems sufficient to just view 
it.

Not sure how much success you'll have finding someone with a SprintPCS 
account...



Reproducible: Always

Steps to Reproduce:
1. www.sprintpcs.com
2. login -> https://manage1.sprintpcs.com/Manage
3. My Online Tools (left) -> https://manage1.sprintpcs.com/Manage?
layer=0&target=MyPlanner&action=intro
4. PCS Mail -> 
http://ucwebf.uc.sprintpcs.com/waimea/servlet/html/mail/ViewFolderServlet;jsessi
onid=CmppE4xCW2U2Nq7DViJOTQz7yaKBR1gKemG6vHHrfBMXoN0s5H2B!-2001657985!169371976!
8000!-1?menubar=email
5. Address Book

Actual Results:  
Firefox crashed

Exception Info
Code: 0xc0000005
Flags: 0
Record: 0
Address: 0


Expected Results:  
not crash

I see dialogs with exciting dump info, but I don't know what becomes of their 
contents. Please tell me how to collect more useful info (traceback, etc.)

Comment 1

[Matthias Versen [:Matti]]

Please provide a talkback ID from the crash.

Comment 2

[Matthias Versen [:Matti]]

no response and not enough informations (Talkback ID, Stack trace)

Comment 3

[A. Sapuntzakis]

I think the problem was that the flashblocker extension didn't survive the 
upgrade from 1.0 to 1.0.1

I uninstalled 1.0 before installing 1.0.1, and my other extensions did OK, but 
flashblocker didn't even show up. However, several Flash sites, including 
SprintPCS, started crashing. I finally followed the manual procedure for 
uninstalling extensions (not trivial!), and the problem seems to have been 
resolved.

http://flashblock.mozdev.org/ mentions a fix in 1.3.0.1 which might be related. 
Maybe this should be forwarded to them?

Not sure why such a minor (?) upgrade had such a drastic impact. I guess it'd 
be nice if Firefox were more robust when it came to malfunctioning extensions, 
but that's probably logged elsewhere.