A tab crashed
A page runs in a process separate from the browser. When that process crashes, is stopped or runs out of memory, the tab shows “Aw, Snap!” and the browser itself keeps running.
What “Aw, Snap!” means
Aw, Snap! with “Something went wrong while displaying this webpage” means the page's process has ended: it crashed on an error, ran out of memory, was stopped in the Task Manager, or Windows kept an outside module out of it. Below are the Error code (what it means is further down), a Reload button and a Learn more link.
If the page crashes again within 10 seconds, the title changes to Can't open this page — or Not enough memory to open this page when memory ran out. Sverk then suggests opening the page in a new Incognito window, restarting Sverk or restarting the computer, and, when memory is short, closing other tabs and programs.
Page Unresponsive
When a page hangs, Sverk shows the Page Unresponsive window: “You can wait for it to become responsive or exit the page.” Wait gives it more time. Exit page stops its process: the tab shows “Aw, Snap!” with RESULT_CODE_HUNG, and you can reload it.
What to do
- Click Reload.
- If memory is short, close tabs and programs you do not need. How much memory each tab uses is shown in ⋮ → More tools → Task manager (Shift+Esc); there you can also stop a hung process with End process. To keep background tabs from holding memory, turn on Memory Saver.
- Open the page in an Incognito window (Ctrl+Shift+N): extensions do not run there by default. If it does not crash there, turn extensions off one by one at
chrome://extensionsuntil you find the one it crashes with. - Update Sverk — here is how.
- Restart Sverk and, if that does not help, the computer.
If the whole browser closed, Sverk does not bring your tabs back by itself at the next start; it asks Restore pages?, and Restore brings them back.
Error codes
The error code names the reason the page's process ended. Some of them:
| Code | What happened |
|---|---|
Out of Memory | the page ran out of memory |
RESULT_CODE_KILLED | the process was stopped, for example with End process in the Task Manager |
RESULT_CODE_HUNG | the page hung and was closed from the Page Unresponsive window |
STATUS_ACCESS_VIOLATION | a program error: memory accessed at an invalid address |
STATUS_BREAKPOINT | an internal check of the browser failed — a bug in Sverk or Chromium |
STATUS_STACK_OVERFLOW | a stack overflow, usually from endless recursion |
STATUS_INVALID_IMAGE_HASH | an outside program tried to load into the page's process, and Windows lets only Microsoft-signed modules in there. Update or remove the program that injects itself into browsers |
If the same codes keep coming on different sites, write to us at support@sverk.ai with the report ID — how to find it is below.
Crash reports
When a tab or the whole browser crashes, Sverk sends a crash report to its own server, not to Google. Sending is on by default: the reports are how we find and fix bugs.
A report carries the Sverk, Windows and device versions, where in the code the error happened, and a memory snapshot of the crashed process. Sverk removes file paths and page addresses from the report's fields before it leaves the computer. The server keeps memory snapshots for 90 days and summaries indefinitely. Usage statistics are not sent anywhere. Details are in the privacy policy.
If you write to us about a crash, open chrome://crashes and copy the Uploaded Crash Report ID: it lets us find your report.
On the computer, crash reports are turned off by the MetricsReportingEnabled policy. Run reg add HKCU\Software\Policies\Sverk /v MetricsReportingEnabled /t REG_DWORD /d 0 /f in a command prompt and restart Sverk. The menu then gets a Managed by your organization item: that is how Sverk marks any policy (more). To send reports again, delete that value.
Didn't find the answer?
Write to us at support@sverk.ai: what you did, what you expected to see and what you saw. Other topics are in the help contents.