Troubleshooting
Common issues and fixes.
"The page is using too much memory"
DuckViz monitors real browser memory (JS heap + IndexedDB + DuckDB). When usage crosses your system's adaptive threshold, a non-closable modal appears.
Fix: Click any table in the memory popover to unmount it, or choose Upload → Start fresh to wipe the session. Closing other browser tabs also helps.
Log files show up as "unparsed"
The log parser uses an LLM-detected format on ingest. If some lines don't match the detected pattern, they land in the Unparsed tab of the file panel. Select them, click Generate Pattern & Ingest, and DuckViz will ask the LLM for a different pattern and append the newly parsed rows to the same table.
CLI browser tab never opens
The CLI tries to open your default browser automatically. If it doesn't:
- Copy the URL printed in the terminal.
- Open it manually in the browser where you're signed in.
- The transfer will continue from there.
If the CLI server sits idle for 10 minutes with no browser response it shuts down automatically — just rerun the command.
"No credits" error on an AI action
Check your credit balance in the header badge. If it's zero, you can continue using free features (manual SQL, exports, file uploads) or buy a credit pack. AI actions that fail don't deduct credits.
Something else?
Email support@duckviz.com with your browser, OS, and a short description. We aim to reply within 3 business days.