Closed
Bug 1191382
Opened 10 years ago
Closed 7 years ago
Disable crash reporter on Instantbird
Categories
(Instantbird Graveyard :: Other, defect)
Instantbird Graveyard
Other
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: clokep, Unassigned)
Details
(Whiteboard: [1.6-blocking])
As discussed as the Summit, the first step to disabling our crash server is to disable shipping the crash reporter.
Comment 1•10 years ago
|
||
Do we want to
1) completely disable the crash reporter (ideally, not even build it)
or
2) still build it, but somehow disable the UI and uploading crash reports?
Possible arguments for 2):
Note the crash reporter is currently used to try to determine whether the app crashed on autologin or not:
https://dxr.mozilla.org/comm-central/source/chat/components/src/imAccounts.js#924
Also, we may still want to keep local minidumps, assuming those are useful.
Reporter | ||
Comment 2•10 years ago
|
||
I think we want to 1, not even build it. I'm unsure if there's any benefit to disabling the UI and uploading.
Comment 3•7 years ago
|
||
On the behalf of Florian:
Closing bugs related to the Instantbird UI as WONTFIX, as the development of the standalone chat client Instantbird has stopped. Instantbird users are encouraged to migrate to Thunderbird. The user interface of instant messaging in Thunderbird will feel familiar, as the Thunderbird IM support started as a fork of Instantbird.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•