Closed
Bug 594960
Opened 14 years ago
Closed 14 years ago
Use nsX11ErrorHandler in content processes
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: cjones, Assigned: cjones)
References
Details
Attachments
(1 file)
925 bytes,
patch
|
karlt
:
review+
|
Details | Diff | Splinter Review |
It's very helpful. One-line fix, we're just not init'ing it.
Assignee | ||
Comment 1•14 years ago
|
||
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 2•14 years ago
|
||
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+
Assignee | ||
Comment 3•14 years ago
|
||
(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 ;).
Assignee | ||
Comment 4•14 years ago
|
||
http://hg.mozilla.org/projects/cedar/rev/fe6802772c00
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•