Closed
Bug 987401
Opened 10 years ago
Closed 6 months ago
browser-chrome tests with e10s enabled cause regular child process crashes.
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: markh, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Running the browser-chrome suite with e10s on Windows will often cause the child process to crash - the crashing test doesn't seem consistent, and generally the crashing test doesn't do anything particularly unusual. The following patch causes the test to run with the following prefs set which prevents the crashes. * layers.offmainthreadcomposition.prefer-basic=true * gfx.direct2d.disabled=true * layers.acceleration.disabled=true I've not dug any deeper than this, so apologies in advance for the somewhat vague nature of this.
Comment 1•10 years ago
|
||
On my win8 system the tests appear to be running fine, so I haven't been able to uncover any useful details.
Updated•10 years ago
|
tracking-e10s:
--- → +
Updated•10 years ago
|
Blocks: e10s-tests
Updated•2 years ago
|
Severity: normal → S3
Comment 2•6 months ago
|
||
Unable to reproduce
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•