Closed
Bug 320041
Opened 19 years ago
Closed 17 years ago
Talkback.exe crashes upon submission
Categories
(Core Graveyard :: Talkback Client, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jliebson, Assigned: jay)
Details
(Keywords: hang)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051212 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051212 Firefox/1.5 I have had several instances of this problem recently, including two this afternoon: Firefox crashes; I run Talkback, fill in the report, try to submit the report; Talkback fails the first time. When Talkback tries a second time to submit the report, Talkback.exe itself crashes. Click on an "X" to close Talkback, error message says program is not responding. Reproducible: Sometimes Steps to Reproduce: 1.See the Details box, please. 2. 3. Actual Results: As stated above, Talkback itself crashes. As far as I can tell (and I'm not overly familiar with the program, so I'm not even certain that this is the proper place to file this report) when Talkback crashes, it loses any unfiled reports. For example, my first attempt to file a FF crash report today encountered a Talkback crash. When Talkback opened for the second FF crash, there was no pending report shown in Talkback. Expected Results: For the crash-report mechanism itself not to crash would seem desirable.
Updated•19 years ago
|
Summary: Talkback.exe Crashes Upon Submision → Talkback.exe crashes upon submission
Version: Trunk → 1.8 Branch
Comment 1•19 years ago
|
||
The definition of a crash is that the application, as a process, is no longer running. "Talkback.exe itself crashes. Click on an "X" to close Talkback, error message says program is not responding." What you're describing here is a hang, rather than a crash.
Comment 2•17 years ago
|
||
WFM per reporter "I've not seen the problem for a few years"
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•