Pages and media
When a page stops or crashes
What Arx does when a page's own script keeps it busy, why a page that stopped says what it says, and pages that keep crashing.
A page can get stuck in its own script: it's still open, but it no longer reacts to clicks, keys or scrolling. Arx notices this the way Chrome does, when something you did on the page goes unanswered for 15 seconds.
Wait or Reload
When the page you're looking at stops responding after you used it, Arx shows This page isn't responding over it:
- Wait (Escape) leaves the page alone. If it's still stuck a while later, Arx asks again.
- Reload ends what the page was doing and loads it again. Anything you typed into it and didn't send is lost.
If the page starts responding again by itself, the card goes away.
Arx asks only about the page in front of you, and only after you tried to use it. A page that's busy while you read something else stays quiet.
Other ways out
You don't have to wait for the card. Reloading, going back or forward, typing an address, or closing the tab works on a stuck page too: Arx ends the stuck page first, then does what you asked.
Pages opened by another page's script often share its process. Ending a stuck page ends those too, and they reload.
Pages that aren't stuck
Arx doesn't count these as stuck:
- A page waiting for you to answer its own alert, confirmation or prompt.
- A page Arx paused in the background to save energy.
- A page paused on a breakpoint while its developer tools are open.
When a page stops
A page that ended says why, so you know whether reloading will help:
| The page says | What happened |
|---|---|
| This page crashed. | Something in the page, or in the engine drawing it, failed. |
| This page ran out of memory. | The page used more memory than it's allowed. |
| macOS ended this page, usually to free memory. | Something outside Arx ended it, most often macOS when the Mac ran low on memory. |
| This page stopped responding, so Arx ended it. | You chose Reload on a stuck page, or another way out ended it. |
| This page couldn't start. | Arx couldn't start the page's process. |
| Several pages stopped at once… | Pages ended within a moment of each other, so the cause is probably something they share, not this page. |
Reload opens the page again.
Arx never reloads a page that stopped by itself. If the same page ends three times within a minute on its own, it says This page keeps crashing (or keeps running out of memory). Reload it once something has changed, or close other pages first. Pages ended together and pages Arx ended don't count toward the three.
Assistants
When an assistant's request on a tab times out and the page doesn't answer a quick check, Arx ends the page, loads it again and tells the assistant with pageNotAnswering. The tab's sessionState in the inventory is notAnswering while that happens. Arx does this only while the assistant may still act on that tab, and only if the page is still the one the request was made on. See Working with pages.
A tab whose page ended is failed in the inventory, with a failureReason: crashed, outOfMemory, killed, endedByArx, launchFailed, other, or keepsCrashing and keepsRunningOutOfMemory for a page that ended three times within a minute. An assistant should reload such a tab once at most, and tell you if it keeps failing.