331266 - Talkback will not send crash reports, they remain in endless queue

Status: RESOLVED WORKSFORME

(Core Graveyard :: Talkback Client, defect)

Description

[Allison Carver]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050319
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050319

Mozilla has been crashing or freezing repeatedly when I visit the url above;  however, that site is in beta mode and I'm sure the problem is with them rather than with Mozilla.  The problems is that, other than the first crash report, Talkback will not send reports--they queue up and I cannot send them.  I don't even have id's for them.  I have tried "Send All" and "Send Unsent Incidents", but nothing is being sent.  If this is not a bug, I apologize, but I could not find existing bugs that described this situation and I'm getting frustrated.

Reproducible: Always

Steps to Reproduce:
1.Mozilla crashes (Yuku sucks)
2.Talkback launches
3.Talkback processes and closes withough having sent the report--report stays "In Queue"

Actual Results:  
No reports sent--reports stay "In Queue"

Expected Results:  
Sent the crash report, as it did only once before

I did not find a crish ID that seemed to matcch what I'm experiencing...I've stopped using Mozilla to visit this particular url (Firefox is much more stable there), but I have crash reports queued up that Talkback seems unble to send.

Comment 1

[Stefan [:stefanh]]

--> Core: Talkback.

Comment 2

[Stefan [:stefanh]]

BTW, you might want to try visiting the site with SeaMonkey (the crash is probably fixed): http://www.mozilla.org/projects/seamonkey/

Comment 3

[Taral]

I have the same problem. This is for Firefox stable. The problem is that talkback.mozilla.org is closing connections immediately after accepting them:

  0 ms local > talkback-80: SYN
 33 ms talkback-80 > local: SYN/ACK
 33 ms local > talkback-80: ACK
 56 ms local > talkback-80: "POST "
 67 ms talkback-80 > local: FIN/ACK (socket close, no ACK for "POST ")
 67 ms local > talkback-80: ACK
 92 ms talkback-80 > local: RST ("POST " was not received before socket was closed)

Comment 4

[Taral]

Finally cleared today.

Comment 5

[Jay Patel [:jay]]

FYI:  Sometimes this will happen when the Talkback servers are down or are having issues.  We try to bring them back online as quickly as possible, but sometimes it falls behind in processing for a few days.  Also, I believe the client clears the queue after some number of days (I think 14), so old incidents should go away eventually.  Anyway, with the new and improved crash reporter in Firefox 3, this bug will soon be obsolete. :-)

Comment 6

[Allison Carver]

Attachment: Backlog???

Wow.  I couldn't figure out what you were responding to until I read the details of the original report.  Congratualtions--it took you all only two years and eight days to respond to this bug report.  Is this a last-minute effort to clear the reports you never dealt with before the upgrade, in an attempt to make your record look good?  I use "you" in the general sense, since I'm sure more than one person had responsibility for these bug reports in the  last two years (and eight days).

Thank you for "clearing" the problem, what ever that means, but I disabled Bugzilla approximately two years ago, mainly because I got no useful response and grew weary of waiting.  Good thing I didn't hold my breath.

Absolutely incredible.