Closed Bug 1339435 Opened 7 years ago Closed 7 years ago

Threading assertion failure in profiler_time(const mozilla::TimeStamp& aTime)

Categories

(Core :: Gecko Profiler, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla54
Tracking Status
firefox54 --- fixed

People

(Reporter: jseward, Assigned: n.nethercote)

Details

Attachments

(3 files)

This ..

  double
  profiler_time(const mozilla::TimeStamp& aTime)
  {
    MOZ_RELEASE_ASSERT(NS_IsMainThread());

.. fails.  It was seen running on "Thread 26 DOM Worker".

I had trouble capturing a stack with GDB -- it froze up my desktop --
but finally it crashed in valgrind.  Details in the attachment.
Attached file Crash stack, etc
STR: I am not sure if all of the following are really necessary,
but anyway:

1. Build on Linux with assertions enabled.

2. Start the build and disable e10s [probably not required]

3. Restart.  Click on the profiler's button, then "Settings"
   and change the text in the Threads box to 
   "GeckoMain,Compositor,_,Stream"
   [I don't know whether this is necessary.]

4. Click on "Apply (Restart Profiler)"

5. "Generally use" the profiler for a couple of minutes (start, stop,
   view profile, browse).  It crashes pretty quickly.
Hmm, that's a MOZ_RELEASE_ASSERT, so maybe --enable-debug isn't needed.
Thank you for the report. When I added those assertions, I just stuck them everywhere and then removed the ones that triggered during local execution and a try push. So clearly that was insufficient coverage. It's trivial to remove them; patch coming up shortly.
Assignee: nobody → n.nethercote
Status: NEW → ASSIGNED
Attachment #8837405 - Flags: review?(jseward) → review+
https://hg.mozilla.org/mozilla-central/rev/f0f27caeb444
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: