[e10s] Can't complete the test262 suite




JavaScript Engine
2 years ago
10 months ago


(Reporter: Alexandre Folle de Menezes, Unassigned)


(Blocks: 1 bug, {triage-deferred})

50 Branch
Windows 10
Dependency tree / graph

Firefox Tracking Flags






2 years ago
I am trying to run the test262 suite hosted here:

I am using Firefox Developer Edition (v49.0a2), which cannot complete the test. halfway through the test it stops painting some areas of the tab running the test (they become black), and later the browser stops responding completely.

Comment 1

2 years ago
To see the painting issue, minimize the window running the test and let it run for a while.  When the window is restored, there are a lot of black areas.  Moving the cursor around the page will make some elements to appear, but not all.

Comment 2

2 years ago
I have now tried this with v50.0a2, and still have the same issue.  Actually, instead of hanging the browser it now says "A web page is slowing down your browser.  What you would like to do?".  Maybe this happens with 49.0a2 too, I left it running overnight and never saw it showing this before it stopped responding.

Comment 3

2 years ago
And now I am running with the current stable version (v48.0) and everything seems fine.
What can be going on:
- Some issue with electrolisys, since it is off in the stable version but on in the Dev Edition;
- Some issue with the 64bit version (I am running 32bit for stable and 64bit for Dev Edition);
- Some other issue introduced in v49;

Can I do something else to help diagnosing this?

Comment 4

2 years ago
I have now disabled Electrolysis on v50.0, and it is running fine.  So I am assuming this is an Electrolysis issue. Marking it as such.
Blocks: 516752
Summary: Can't complete the test262 suite → [e10s] Can't complete the test262 suite
tracking-e10s: --- → ?
There are definitely tests that will just hang in the shell, for example built-ins/Array/prototype/slice/S15.4.4.10_A3_T1


2 years ago
tracking-e10s: ? → +

Comment 6

2 years ago
Nightly completed locked up on the "result-get-matched-err" test. It made the content process use 3GB (maximum on my Win7 machine) and use 50% of the CPU total. Had to kill the process.
Keywords: triage-deferred
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.