Closed Bug 830809 Opened 11 years ago Closed 11 years ago

Remove 'shutdown start' label with eConsiderQuit

Categories

(Core :: Gecko Profiler, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla21

People

(Reporter: BenWa, Assigned: BenWa)

References

Details

Attachments

(1 file, 1 obsolete file)

Attached patch patch (obsolete) — Splinter Review
The labels were incorrectly showing up when we were calling with eConsiderQuit. Need to move the label to when we've decided to shutdown.
Attachment #702344 - Flags: review?(vdjeric)
Attachment #702344 - Flags: review?(vdjeric) → review+
Attachment #702344 - Flags: review+ → feedback+
Attachment #702344 - Flags: review?(ehsan)
Comment on attachment 702344 [details] [diff] [review]
patch

Review of attachment 702344 [details] [diff] [review]:
-----------------------------------------------------------------

::: toolkit/components/startup/nsAppStartup.cpp
@@ +361,5 @@
>    }
>  
>    nsCOMPtr<nsIObserverService> obsService;
>    if (ferocity == eAttemptQuit || ferocity == eForceQuit) {
> +    SAMPLE_MARKER("Shutdown start");

If you're interested in the point of no return, that's further down this function, where we set mShuttingDown = true.  The new place for the marker can also be too early since we may be unable to close some of our windows.
Attachment #702344 - Flags: review?(ehsan) → review-
Attached patch patch v2Splinter Review
Alright this means we could potentially miss quite a bit of work:
1) We can either assume the user will look at the samples a bit before this marker
2) Or we could have a shutdown cancel marker as well.

This patch does 1 which I think is ok.
Assignee: nobody → bgirard
Attachment #702344 - Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #702427 - Flags: review?(ehsan)
Attachment #702427 - Flags: review?(ehsan) → review+
Rafael, does the bug addressed in this patch imply we might be recording the shutdown timestamp multiple times during a session?
Flags: needinfo?(respindola)
(In reply to Vladan Djeric (:vladan) from comment #3)
> Rafael, does the bug addressed in this patch imply we might be recording the
> shutdown timestamp multiple times during a session?

Yes, but "recording" in here is just setting a global variable. 

void
RecordShutdownStartTimeStamp() {
  if (!Telemetry::CanRecord())
    return;

  gRecordedShutdownStartTime = TimeStamp::Now();

  GetShutdownTimeFileName();
}

Which should be a nop. In any case, we would probably move it to the earliest point we know firefox will be shutdown and make sure it is called only once.
Flags: needinfo?(respindola)
When do we call with eConsiderQuit? I have done to try pushes to check this:

Just add an assert:
https://tbpl.mozilla.org/?tree=Try&rev=bbd6c5d33b88

Add the assert and move:
 https://tbpl.mozilla.org/?tree=Try&rev=062eb1142bb5

I will probably send the second one (rebased on top of this) for review if it is green.
I reported bug 831303 to fix the mozilla::RecordShutdownStartTimeStamp call.
https://hg.mozilla.org/mozilla-central/rev/712eca11a04e
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: