Open Bug 1619152 Opened 6 years ago Updated 3 years ago

The ARES-6 benchmark fails when restored from previous session

Categories

(Firefox :: Session Restore, defect, P3)

Desktop
macOS
defect

Tracking

()

REOPENED
Tracking Status
firefox75 --- affected

People

(Reporter: mgol, Unassigned)

Details

The ARES-6 benchmark crashes on start.

Steps to reproduce:

  1. Open https://browserbench.org/ARES-6/index.html
  2. Click START.

The "START" button text changes to "Test failure — error in console", and the console displays:

Error encountered:  ReferenceError: AirBenchmark is not defined https://browserbench.org/ARES-6/index.html line 170 > scriptElement 32 17 ReferenceError: "AirBenchmark is not defined"
    <anonymous> https://browserbench.org/ARES-6/index.html line 170 > scriptElement:32
    _iterate https://browserbench.org/ARES-6/driver.js:170
    setTimeout handler*_iterate https://browserbench.org/ARES-6/driver.js:161
    start https://browserbench.org/ARES-6/driver.js:73
    driver https://browserbench.org/ARES-6/glue.js:31
    readyTrigger https://browserbench.org/ARES-6/driver.js:49
    <anonymous> https://browserbench.org/ARES-6/glue.js:54

followed by a bunch of warnings like:

‘src’ attribute of <script> element is not a valid URI: “Air/symbols.js”

The benchmark fails in Nightly 75.0a1 (2020-02-29) & 75.0a1 (2020-03-01). It worked in recent Nightly versions, I think even in the immediately preceding one to the one from 2020-02-29.

crashes? or fails to run?

2020-02-24 seems to work. And so does 2020-03-01.

Flags: needinfo?(m.goleb+mozilla)

Sorry, I see the "crash" word is confusing here. The browser doesn't crash, the test just fails instantly with an error in a way I described in my original comment.

Flags: needinfo?(m.goleb+mozilla)

(In reply to Olli Pettay [:smaug] from comment #1)

2020-02-24 seems to work. And so does 2020-03-01.

I've just tested on a fresh profile in Nightly and the test doesn't fail instantly there, indeed. That said:

  1. I haven't changed anything in my main Nightly profile for the past few days (& even more) & it worked fine a few days ago.
  2. I don't have any extensions installed on that profile.

It might be that I enabled something in about:config long ago and that setting broke right now. Is there any way in which I could find the real issue here?

Is there any way in which I could find the real issue here?

I don't know.

Works for me on 2020-03-01 Nightly on Linux.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME

Going to about:support & clicking "Refresh Nightly" resolved the issue for me on my main profile.

Oh, no, it doesn't. Here's what I did:

  1. Open Nightly with my main Nightly profile.
  2. Go to about:support and click "Refresh Nightly".
  3. After restart choose "Restore windows & tabs".
  4. Go to settings, check "Startup -> Restore previous session".
  5. Run the ARES-6 benchmark => it works
  6. Restart the browser.
  7. Run the ARES-6 benchmark => it fails as above.

AFAIK refreshing Nightly should have reset any custom about:config setup, etc. Might there still be an issue to investigate here, perhaps?

OK, I have a test case that doesn't depend on any preexisting profile data:

  1. Create a new profile for Nightly & open Nightly with it.
  2. Go to about:preferences, enable "Startup -> Restore previous session".
  3. Open https://browserbench.org/ARES-6/index.html in a new tab, click "START".
  4. Quit the browser (no need to finish the test).
  5. Open the browser again, it will open the ARES-6 page.
  6. Click "START".

You'll now see the errors I described above & it never goes back to normal.

I can reproduce it in Nightly, Dev Edition, stable (73.0.1) & even latest ESR (68.5.0esr). I cannot reproduce it in Chrome 80.0.3987.122 or Safari 13.0.5 (15608.5.11), both latest stable.

Reopening for further investigation since it's Firefox-only and has steps to reproduce.

Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Component: DOM: Core & HTML → Session Restore
Product: Core → Firefox

The priority flag is not set for this bug.
:mikedeboer, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(mdeboer)
Severity: normal → S3
Flags: needinfo?(mdeboer)
Priority: -- → P3
Summary: The ARES-6 benchmark crashes on start → The ARES-6 benchmark fails when restored from previous session

Hi, I'm doing bug triage and I'm trying to understand the importance of this and whether this is still an issue.

Flags: needinfo?(m.goleb+mozilla)

I've just checked and yes, this is still an issue.

Flags: needinfo?(m.goleb+mozilla)
You need to log in before you can comment on or make changes to this bug.