If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Use nsX11ErrorHandler in content processes

RESOLVED FIXED

Status

()

Core
Graphics
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: cjones, Assigned: cjones)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

It's very helpful.  One-line fix, we're just not init'ing it.
Created attachment 473753 [details] [diff] [review]
Use nsX11ErrorHandler in content processes

We'll want to eventually hook this into crash reporting as well, when that's hooked up for content processes.
Assignee: nobody → jones.chris.g
Attachment #473753 - Flags: review?(karlt)
Comment on attachment 473753 [details] [diff] [review]
Use nsX11ErrorHandler in content processes

This part looks fine, but don't you also need something here?:
http://hg.mozilla.org/mozilla-central/annotate/743e2ea36e51/toolkit/xre/nsX11ErrorHandler.cpp#l146
Attachment #473753 - Flags: review?(karlt) → review+
(In reply to comment #2)
> Comment on attachment 473753 [details] [diff] [review]
> Use nsX11ErrorHandler in content processes
> 
> This part looks fine, but don't you also need something here?:
> http://hg.mozilla.org/mozilla-central/annotate/743e2ea36e51/toolkit/xre/nsX11ErrorHandler.cpp#l146

Yes, when we have content-process crash reporting ;).
http://hg.mozilla.org/projects/cedar/rev/fe6802772c00
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Depends on: 601267
You need to log in before you can comment on or make changes to this bug.