Memory, CPU & Crashes

Docs › App Hosting

Memory, CPU & Crashes

What happens when your app uses more than its size, or stops.

BuildingInstalls and builds get extra memory, so a Next.js build does not fail on a small size. Once the app answers, it is held to its size.
MemoryA hard limit. An app that goes over it is stopped by the system (out of memory). NOVA notices within seconds and starts it again, without rebuilding, so it is back in seconds.
CPUA share, not a limit that stops the app. Past it, the app is slowed, never stopped. The CPU graph shows it at its size.
CrashesAn app that stops for any other reason (an error it doesn't handle) is started again the same way.
Crash loopsIf it stops 5 times in 10 minutes, NOVA leaves it stopped instead of restarting it for ever. Visitors see a short notice until you deploy a fix.

Each restart is on the app's Events with the reason, and you get an email (at most once a day per app) saying what happened and why: out of memory, or the error line from the end of its log. If it keeps running out of memory, choose a bigger size, or look for memory it holds on to.

Ask NOVA to fix it

  1. 1Press Ask NOVA to fix this beside the newest problem in Events, or just tell NOVA in the chat, for example "my live site crashed".
  2. 2NOVA reads the live app's log and timeline, finds the cause in the code, fixes it, and starts the app to check the fix.
  3. 3It tells you in plain words what was wrong and what it changed. Nothing goes live until you press Make Live or Deploy, and you can push the fix to GitHub from the GitHub tab.

Join our Discord

Chat with our engineers and become part of the active NOVA developer community.

Join Discord

Need help?

Open an issue on GitHub or email support@bridgeye.com.

Get help
Bridgeye • Autonomous Software Engineering.