657523 - Firefox 4 & 5 crash with new Yahoo! Mail Beta (but 3.6.x doesn't)

Status: RESOLVED DUPLICATE of bug 655660

(Firefox :: General, defect)

Description

[mily]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17 ( .NET CLR 3.5.30729; .NET4.0E)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17 ( .NET CLR 3.5.30729; .NET4.0E)

Keep deleting a message from the message list or from within the message view in a message tab. Eventually the browser will cras. Crash details from FF :


AdapterDeviceID: 0000
AdapterVendorID: 0000
Add-ons: [e-mail]:2.3.2.0,[e-mail]:1.7.1,[e-mail]:1.1.1,{972ce4c6-7e08-4474-a285-3208198ce6fd}:4.0.1
AvailableVirtualMemory: 1561747456
BuildID: 20110413222027
CrashTime: 1305566780
EMCheckCompatibility: true
Email: [e-mail]
FramePoisonBase: 00000000f0de0000
FramePoisonSize: 65536
InstallTime: 1304631743
Notes: AdapterVendorID: 0000, AdapterDeviceID: 0000, AdapterDriverVersion: , , \REGISTRY\Machine\System\CurrentControlSet\Services\RDPDD\Device0
D3D10 Layers? D3D10 Layers-
D3D9 Layers? D3D9 Layers-

ProductName: Firefox
ReleaseChannel: release
SecondsSinceLastCrash: 674
StartupTime: 1305566139
SystemMemoryUsePercentage: 57
Theme: classic/1.0
Throttleable: 1
TotalVirtualMemory: 2147352576
Vendor: Mozilla
Version: 4.0.1
Winsock_LSP: MSAFD Tcpip [TCP/IP] : 2 : 1 : %SystemRoot%\system32\mswsock.dll
 MSAFD Tcpip [UDP/IP] : 2 : 2 : 
 MSAFD Tcpip [RAW/IP] : 2 : 3 : %SystemRoot%\system32\mswsock.dll
 MSAFD Tcpip [TCP/IPv6] : 2 : 1 : 
 MSAFD Tcpip [UDP/IPv6] : 2 : 2 : %SystemRoot%\system32\mswsock.dll
 MSAFD Tcpip [RAW/IPv6] : 2 : 3 : 
 RSVP TCPv6 Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll
 RSVP TCP Service Provider : 2 : 1 : 
 RSVP UDPv6 Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll
 RSVP UDP Service Provider : 2 : 2 : 
 VMCI sockets DGRAM : 0 : 2 : 
 VMCI sockets STREAM : 0 : 1 : C:\Program Files\VMware\VMware Tools\VSock SDK\bin\win32\vsocklib.dll
 MSAFD Pgm (RDM) : 2 : 4 : %SystemRoot%\system32\mswsock.dll
 MSAFD Pgm (Stream) : 2 : 1 : 
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{DE7105DB-1D56-4E80-8E7A-7677024768ED}] SEQPACKET 1 : 2 : 5 : %SystemRoot%\system32\mswsock.dll
 MSAFD NetBIOS [\Device\NetBT_Tcpip_{DE7105DB-1D56-4E80-8E7A-7677024768ED}] DATAGRAM 1 : 2 : 2 : 
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{AF2408F6-3F97-48A2-95AB-D5A90C566F01}] SEQPACKET 0 : 2 : 5 : %SystemRoot%\system32\mswsock.dll
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{AF2408F6-3F97-48A2-95AB-D5A90C566F01}] DATAGRAM 0 : 2 : 2 : 
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{811F56CE-8BE0-46D1-87F6-8DB2C8AC9032}] SEQPACKET 3 : 2 : 5 : %SystemRoot%\system32\mswsock.dll
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{811F56CE-8BE0-46D1-87F6-8DB2C8AC9032}] DATAGRAM 3 : 2 : 2 : 
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{DE7105DB-1D56-4E80-8E7A-7677024768ED}] SEQPACKET 2 : 2 : 5 : %SystemRoot%\system32\mswsock.dll
 MSAFD NetBIOS [\Device\NetBT_Tcpip6_{DE7105DB-1D56-4E80-8E7A-7677024768ED}] DATAGRAM 2 : 2 : 2 :

This report also contains technical information about the state of the application when it crashed.

Reproducible: Always

Steps to Reproduce:
1. Open yahoo! Mail beta - mail.yahoo.com
2. Click on a message in the message list to open it in a tab (need 30-50 messages for deleting)
3. Click the delete button continuously - at some point the browser will crash

Actual Results:  
Browser crashes (but not in 3.6.x)

Expected Results:  
No crash

Comment 2

[Marcia Knous [:marcia]]

Are you able to reproduce this consistently? Or does it only happen intermittently?

Comment 3

[mily]

I am able to reproduce it consistently but it takes a while (about 30 deletes) - some other internal Y!Mail beta testers indicate they can get it to crash sooner

Comment 4

[Daniel Veditz [:dveditz]]

(In reply to comment #0)
> Crash details from FF :

Unfortunately that's the mostly uninteresting machine-configuration part. We show that to people who might be concerned about what kind of information we're gathering. In the case of mysterious hard-to-reproduce crashes that information helps us to find patterns, like whether it's happening only to people who have a particular add-on installed or a specific graphics driver, that kind of thing.

> This report also contains technical information about the state of the
> application when it crashed.

That's the part we really wanted -- where did the program crash and what was it doing. You can get that information (if you submitted the crash to us) by opening the page about:crashes and getting a list of your crashes. Just copy the crash ID and paste it into the bug. Preferably just the ID rather than the link -- anything that starts with "bp-" and is in the right format will be auto-linked in bugzilla and is therefore more compact and easier to read. Though if you paste in the crash-stats link itself no one's going to complain.

Comment 5

[Marcia Knous [:marcia]]

mily: anything you can do to give us a set of consistent steps would be really helpful and help us with Bug 655660. If there are other internal Y!Mail beta testers that can add other helpful ideas, would love to hear them. I still haven't been able to reproduce the crash with my account.

Comment 6

[mily]

The one consistent step I've reproduced 100% was launching Y! Mail Beta on Windows 7, with FF 4.x. I would go into a folder and start deleting the emails by hitting the delete key and about 20-30 deletes later, FF would crash - happened every time.

Is there any specific data I can collect and send? I just sent the crash report that was associated with the crash dialog from FF - 

Would you be amenable to a web conference session? Maybe thats something we can set up.

Comment 7

[Marcia Knous [:marcia]]

mily: I will try these steps again in my QA lab to see if I can reproduce. Otherwise I am definitely amenable to doing a web conference.