Open Bug 1489536 Opened Last year Updated 7 months ago

If a content process triggers the exception handler it can cause a race in the crash reporting code


(Toolkit :: Crash Reporting, defect)

Not set




(Reporter: gsvelto, Unassigned)



When a content process crashes we temporarily store crash information inside a pid-indexed hash table and once we have all the data we remove it from there and write out the crash report. However if the content processes triggers the exception handler again before we've finalized the previous crash report we'll race against the previous iteration or hit this assertion:

While this scenario is rare we've seen it happen in bug 1483862 so we should fix this issue.
You need to log in before you can comment on or make changes to this bug.