Critical Root Cause Found: Solving Infinite Loading, SQLITE_CORRUPT, and MongoDB Hallucinations in AI Studio (March 2026)

Google AI Studio
,
1

Hi everyone,

After struggling with the “2026 Stability Crisis” for several days—experiencing the black preview screen, infinite loading loops, and “Restore” failures—I’ve identified a specific technical “smoking gun” that may be affecting many of you.

The “Smoking Gun”: Transitive Dependency Hallucinations

If you are seeing the AI suddenly trying to add MongoDB or Mongoose to your project even if you never used them, check your dependency tree. In my case, using the natural library (v8.1.1) was the trigger. It pulls in mongoose as a transitive dependency, which leads the new AI Studio agent backend to incorrectly assume your project requires a NoSQL stack.

This causes a fatal EUSAGE sync error because the AI edits the package.json but fails to update the package-lock.json correctly.

The Fatal Error: SQLITE_CORRUPT

The loading failure isn’t just a UI glitch. I found that the platform’s backend orchestration is frequently corrupting SQLite databases during the initial browser handshake. If you see SQLITE_CORRUPT: database disk image is malformed in your logs, the app will never load until the file is reinitialized.

The “Nuclear” Recovery Checklist

If your app is stuck, I found this sequence to be the only reliable fix:

  1. Identify and Remove Bloat: Specifically check for libraries like natural that pull in unwanted database drivers.

  2. Force a Lockfile Purge: Delete package-lock.json and run a fresh npm install to clear the “ghost” dependencies.

  3. Reinitialize the DB: Rename your vizkard.db to .corrupt and use a dedicated db_init script to recreate your tables from scratch.

  4. Environment Reset: Create a “Remix” of your app to force the backend to assign a fresh container.

I’ve documented this in a fixes.md file within my project /docs folder to refer the AI back whenever it enters a “hallucination loop.” Hopefully, this helps others get their builds working again while Google stabilizes the backend.

These problems are so frequent that I am hitting most of my free tier usage and having to switch to api just to fix them repeatedly.
Encountered retryable error from model provider: Agent execution terminated due to error.errorQuota limits exceeded, then when prompted to retry it retries competely unrelated actions.

At this point it really feels like Google AI Studio is severely broken and almost unusable. If I were google I’d take the product offline or restore it to its previous state which worked 4 or 5 days ago. All AI Studio usage for the upgrade problematic period related costs on app building API’s should be refunded to all users as a credit applied to their cloud account.