Closed
Bug 406718
Opened 17 years ago
Closed 17 years ago
add logging to file support to assist troubleshooting
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
FIXED
mozilla1.9beta3
People
(Reporter: robert.strong.bugs, Assigned: mossop)
References
Details
(Whiteboard: need ans. to comment 6)
Attachments
(1 file)
(deleted),
patch
|
robert.strong.bugs
:
review+
dveditz
:
approval1.8.1.12-
mtschrep
:
approval1.9+
|
Details | Diff | Splinter Review |
spinoff of Bug 396695 to assist in the future for bugs that need logging during startup.
Assignee | ||
Comment 1•17 years ago
|
||
This adds file logging for certain failure cases that shouldn't happen in normal use. It also removes the now redundant updateTargetAppInfo function.
Assignee: nobody → dtownsend
Status: NEW → ASSIGNED
Attachment #291390 -
Flags: review?(robert.bugzilla)
Assignee | ||
Updated•17 years ago
|
Whiteboard: [has patch]
Reporter | ||
Comment 2•17 years ago
|
||
Comment on attachment 291390 [details] [diff] [review]
patch rev 1
Looks good.
Attachment #291390 -
Flags: review?(robert.bugzilla) → review+
Reporter | ||
Updated•17 years ago
|
Whiteboard: [has patch] → [has patch][has review]
Assignee | ||
Comment 3•17 years ago
|
||
Comment on attachment 291390 [details] [diff] [review]
patch rev 1
This adds logging for the generally never reached failure cases in the extension manager. This is important to allow us to track down what might have caused problems on a user's machine when we can't reproduce locally.
Attachment #291390 -
Flags: approval1.9?
Updated•17 years ago
|
Attachment #291390 -
Flags: approval1.9? → approval1.9+
Assignee | ||
Comment 4•17 years ago
|
||
Checking in toolkit/mozapps/extensions/src/nsExtensionManager.js.in;
/cvsroot/mozilla/toolkit/mozapps/extensions/src/nsExtensionManager.js.in,v <-- nsExtensionManager.js.in
new revision: 1.266; previous revision: 1.265
done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
OS: Windows Vista → All
Hardware: PC → All
Resolution: --- → FIXED
Whiteboard: [has patch][has review]
Target Milestone: --- → Firefox 3 M11
Assignee | ||
Comment 5•17 years ago
|
||
Comment on attachment 291390 [details] [diff] [review]
patch rev 1
This has been on trunk for a few weeks with no reported issues and it's existance means that we can gather far more detailed information about problems during startup than was previously possible so requesting branch approval. As per the previous trunk approval request this only really has any effect when things are going wrong anyway and in that case just writes some additional information to a disk based log file.
Attachment #291390 -
Flags: approval1.8.1.12?
Comment 6•17 years ago
|
||
Comment on attachment 291390 [details] [diff] [review]
patch rev 1
Looks mostly OK, but how big is this log file going to get, and how would a user clear it/know about it?
Updated•17 years ago
|
Whiteboard: need ans. to comment 6
Assignee | ||
Comment 7•17 years ago
|
||
(In reply to comment #6)
> (From update of attachment 291390 [details] [diff] [review])
> Looks mostly OK, but how big is this log file going to get, and how would a
> user clear it/know about it?
Currently there is no way to clear the log. However I would not expect it to be getting large, it should only ever be written to when there is something wrong happening that would be leading to problems using extensions in the first place.
Comment 8•17 years ago
|
||
Comment on attachment 291390 [details] [diff] [review]
patch rev 1
Have to turn this down for the branch, it's a "nice to have" but we'd really like to see how it goes on the trunk for a bit first.
Attachment #291390 -
Flags: approval1.8.1.12? → approval1.8.1.12-
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•