Closed Bug 1252089 Opened 9 years ago Closed 9 years ago

Properly report in the crash metadata which sanitization promise we are currently blocked on

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 47
Tracking Status
firefox45 --- wontfix
firefox46 --- fixed
firefox47 --- fixed

People

(Reporter: mak, Assigned: mak)

References

Details

Attachments

(1 file)

At the moment we report which sanitizations completed, but we don't report which sanitization we are waiting. Would be useful to know what is blocking when we abort, to direct investigations.
Comment on attachment 8724808 [details] MozReview Request: Bug 1252089 - Report the in-progress sanitization in shutdown abort metadata. r=yoric https://reviewboard.mozilla.org/r/37161/#review33713 Looks good to me. Two minor suggestions. ::: browser/base/content/sanitize.js:156 (Diff revision 1) > - // Name is the itemName and promise may be a promise, if the sanitization > + // Name is the item's name and promise may be a promise, if the sanitization Let's take the opportunity to make this `name` and `promise` (with backquotes). ::: browser/base/content/sanitize.js:162 (Diff revision 1) > - // Note we need to catch errors here, otherwise Promise.all would stop > + let item = this.items[name]; We could take the opportunity to annotate `progress[itemName] = "started"`.
Attachment #8724808 - Flags: review?(dteller) → review+
https://reviewboard.mozilla.org/r/37161/#review33713 > We could take the opportunity to annotate `progress[itemName] = "started"`. in the current situation "ready" and "started" would be the same thing, cause we start all the items at the same time.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 47
Comment on attachment 8724808 [details] MozReview Request: Bug 1252089 - Report the in-progress sanitization in shutdown abort metadata. r=yoric Approval Request Comment [Feature/regressing bug #]: no regression [User impact if declined]: The current metadata we get when sanitize aborts on shutdown is not really useful to understand where we block, this should allow us to better understand the problem and see which sanitize items need intervention. [Describe test coverage new/current, TreeHerder]: nightly [Risks and why]: low risk, trivial code changes [String/UUID change made/needed]: none
Attachment #8724808 - Flags: approval-mozilla-aurora?
Comment on attachment 8724808 [details] MozReview Request: Bug 1252089 - Report the in-progress sanitization in shutdown abort metadata. r=yoric Here's hoping this improves our shutdown hang/crash data for 46.
Attachment #8724808 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
[bugday-20160323] Status: RESOLVED,FIXED -> UNVERIFIED Comments: STR: Not clear. Developer specific testing Component: Name Firefox Version 46.0b9 Build ID 20160322075646 Update Channel beta User Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0 OS Windows 7 SP1 x86_64 Expected Results: Developer specific testing Actual Results: As expected
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: