Closed
Bug 363564
Opened 18 years ago
Closed 18 years ago
Unexpected crash after clicking on Submit button
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: ronald.gold, Unassigned)
References
()
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.7) Gecko/20060911 Camino/1.0.3
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.7) Gecko/20060911 Camino/1.0.3
Camino crashed after I filled out a Sympatico.Ca survey form and clicked on the Submit button.
Reproducible: Always
Steps to Reproduce:
1.Complete form
2.Click on Submit Button
3.
Actual Results:
After clicking on Submit button, spinning beach ball appeared and then Camino crashed. Crash reproduced two more times when I relaunch Camino, opened Sympatico Survey page, completed form and clicked on Submit button.
Talk Back reports sent after each crash:
TB27220036G
TB27220362G
TB27220506K
Crash reports for crashes to be submitted after filing bug.
Reporter | ||
Comment 1•18 years ago
|
||
Comment 2•18 years ago
|
||
This crash is in the 3rd-party 1Passwd; it's not Camino's fault.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 3•18 years ago
|
||
(In reply to comment #2)
> This crash is in the 3rd-party 1Passwd; it's not Camino's fault.
>
Could you please explain how the fault is 1Passwd's? The developer of 1Passwd has released an update which was supposed to take care of thie problem, which I had reported before (Bug 362114). I installed the updated 1Passwd (version 2.1) and had been crash free for a week until today.
Updated•18 years ago
|
Status: RESOLVED → VERIFIED
Comment 4•18 years ago
|
||
(In reply to comment #3)
> (In reply to comment #2)
> > This crash is in the 3rd-party 1Passwd; it's not Camino's fault.
> >
>
> Could you please explain how the fault is 1Passwd's?
The crash occurs in 1Passwd code, not Camino's. Just because the developer thinks he solved one crash doesn't mean there isn't another that he overlooked the first time. The two crash logs confirm this -- they have different stacks, and solving the first crash problem appears to have exposed another one.
Please do NOT report bugs in Bugzilla if you have ANY third-party add-ons installed. Report them to the developer, remove ALL add-ons, and if the problem persists with out ANY add-ons, you may report the bug here.
cl
You need to log in
before you can comment on or make changes to this bug.
Description
•