Closed
Bug 548208
Opened 14 years ago
Closed 14 years ago
Port Bug 411930 [Crash reporter sends wrong URL when crashing during pageload] to SeaMonkey
Categories
(SeaMonkey :: Session Restore, defect)
SeaMonkey
Session Restore
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.1a1
People
(Reporter: misak.bugzilla, Assigned: misak.bugzilla)
References
Details
Attachments
(1 file)
|
355 bytes,
patch
|
neil
:
review+
neil
:
superreview+
|
Details | Diff | Splinter Review |
From parent bug: I just had FF 3 beta 2 crash, and the crash reporter got launched. I looked at the report and saw that the URL it was going to report was the URL of an active tab, which was just a simple page showing contents of a local file. I don't think the problem was on that page. FF was downloading 3 large files at the time. Since FF is a multipage browser, ALL URLs need to be recorded if the exact one associated with the problem can't be identified.
Attachment #428647 -
Flags: superreview?(neil)
Attachment #428647 -
Flags: review?(neil)
|
||
Updated•14 years ago
|
Attachment #428647 -
Flags: superreview?(neil)
Attachment #428647 -
Flags: superreview+
Attachment #428647 -
Flags: review?(neil)
Attachment #428647 -
Flags: review+
|
Assignee | |
Updated•14 years ago
|
Keywords: checkin-needed
|
||
Comment 1•14 years ago
|
||
Comment on attachment 428647 [details] [diff] [review] patch [Checkin: Comment 2] http://hg.mozilla.org/comm-central/rev/7e6d3908a938
Attachment #428647 -
Attachment description: patch → patch
[Checkin: Comment 1]
|
|
||
Comment 2•14 years ago
|
||
Comment on attachment 428647 [details] [diff] [review] patch [Checkin: Comment 2] (In reply to comment #1) > http://hg.mozilla.org/comm-central/rev/7e6d3908a938 http://hg.mozilla.org/comm-central/rev/908177e763f6 !
Attachment #428647 -
Attachment description: patch
[Checkin: Comment 1] → patch
[Checkin: Comment 2]
|
|
||
Updated•14 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.1a1
You need to log in
before you can comment on or make changes to this bug.
Description
•