Recovery, Storage, and Troubleshooting
Chapter 6: Recovery, Storage, and Troubleshooting
Chrome will interrupt the extension. It's not a question of if — service workers sleep on idle, tabs get closed, Chrome reclaims memory under pressure. This chapter is how the extension survives, and what to do when the seams show.
The recovery model in one paragraph
Every recording writes its audio (and video) to IndexedDB, the browser's local database, as it happens. When you are signed in, each part is also uploaded and the local copy is trimmed once that part is safely in the cloud. Without an account, the whole recording stays on your device. If Chrome stops the extension mid-recording, what was written stays behind. Next time you open the side panel, it appears in the list of recordings saved on this device: signed-in users can upload it, continuing from the parts already in the cloud; without an account you can download it or sign in to save it. Nothing is silently lost.
The "saved on this device" list
It appears in the side panel whenever recordings are kept on the device, headed N recordings saved on this device (). Each row shows:
- The meeting title (or "Untitled —
<date>" for recordings that never got a title). - Length, size and date.
- A chip saying where the recording is:
- Partial: some parts are already in the cloud; an upload continues from there.
- Local: only on this device.
- Upload failed: the last upload attempt for this recording failed. You can try again.
- Download and Delete on every row, plus Upload when you are signed in. While it runs, the button reads Uploading….
The list shows two recordings at a time; use the arrows and the page counter below it to see the rest.
At the top of the list:
- Upload all (signed in) uploads every recording in the list.
- Sign in to save all (not signed in) signs you in, then uploads them.
- Delete all deletes every local recording.
After a recording uploads, it leaves the list and the panel notes N recording(s) uploaded to cloud. Recordings that finished uploading are not shown.
When Chrome kills the extension mid-recording
Any of these can happen and are handled:
- The tab you're recording is closed. The recording stops and saves as if you had clicked Stop; the panel says The recording tab was closed — recording saved.
- You close the side panel. The recording keeps going. Reopen the panel to see it.
- The recording tab crashes. The mic content-script relay dies; after 5 seconds of no PCM frames the side panel shows a "microphone signal was lost" warning. The recording is stopped and the chunks captured up to that point are staged for recovery.
- The service worker is recycled by Chrome. On next cold-start the extension pings the offscreen document; if it responds, the recording continues seamlessly, if not, the offscreen is abandoned and the panel returns to setup with the staged chunks intact.
- The offscreen document is reclaimed under memory pressure. Its
pagehidehandler force-stops the recording. A 30-second mic-signal-stall backstop inside the offscreen also stops the recording if every external signal is lost. - The browser is closed while recording. The recording appears in the list of recordings saved on this device next time you open the side panel.
The one case that used to be silently lossy — a Google Meet meeting ending in a single-page-app navigation — is handled by the service worker watching for the tab leaving the meeting-code URL directly, independent of the content script.
When an upload fails
A dropped connection during a recording doesn't end it. The upload pauses, the recording is kept on your device, and the upload retries for a few minutes, waiting while you're offline. If it still can't finish:
- The panel says Upload interrupted — recording saved on this device. Retry from the local recordings list.
- The recording is in the list of recordings saved on this device, marked Partial (some parts made it) or Upload failed.
- Signed in: Upload on that row continues from the parts already in the cloud, so a long meeting isn't uploaded again from the start.
- Not signed in: Download saves the recording to your computer (as
.mp4or.webm, depending on how it was recorded), or Sign in to save all uploads it to your new account.
The extension doesn't retry on a timer after that; use Upload or Upload all.
Storage management
Local recordings are not auto-deleted after 30 days any more. If you treat the extension as a standalone recorder — recording meetings, keeping the files locally, never signing in — old recordings used to disappear silently. That's fixed.
Only two categories are auto-cleaned safely:
- Finalized orphans — the upload confirmed the recording is safely in R2, and the local copy is now redundant.
- 0-byte orphans — the recording died before any audio was captured; nothing to recover.
At 500 MB of staged local recordings, a yellow storage warning appears at the top of the side panel. It's advisory — no data is deleted — but it's a nudge to sign in and upload, or download and clear.
To clear a specific recording, click Delete on its row; Delete all clears the whole list. Both ask you to confirm (This cannot be undone.), and warn when unuploaded notes would be deleted too.
Common problems
"The extension icon is greyed out on chrome://, edge://, or the Chrome Web Store."
Chrome forbids extensions from running on chrome:// pages, edge:// pages, and the Chrome Web Store itself. This is a browser-wide restriction; nothing SeaMeet can do. Open the meeting in a normal tab.
"Tab capture failed with 'Cannot access a chrome:// URL' or 'Extension not allowed for this tab'."
The tab was open before you installed the extension. Chrome refuses to attach tab-capture to a tab that has no permission grant. Reload the tab and try again.
"Recordings show as 0:00 in the recovery list."
This was a bug in older versions — the duration was written only at stop time, so an interrupted recording had none. It's now persisted during the recording, so this only happens if the recording ended before the first duration update. Falls back to — when unknown.
"The uploaded file plays but shows unknown / infinite duration."
Recordings up to 100 MB have their duration metadata rewritten before upload completes, so this is fixed for those. Larger or resumed recordings keep the Part-1 patch fallback — the file plays, but a small number of players may not seek correctly. Try VLC as a workaround.
"The Meet meeting ended but the recording kept going."
This class of bug was fixed in 1.9. If it happens on 1.9 or later, please report — with the version number from chrome://extensions/ and a note on the meeting platform.
"The captions stopped in the middle of the meeting."
The live speech-to-text reconnects by itself a few times; if that fails, a Retry captions button appears in the transcript area. Click it. The recording keeps going the whole time — no audio is lost.
"A recording from a Meet call has the wrong title (the tab title)."
This was fixed in 1.8 — extension recordings now start as "Untitled — <date>", matching the web app's default-name guard, so the AI-generated meeting title correctly replaces it after upload. If you see this on 1.8 or later, the AI rename usually catches up within a minute.
When to file a bug
- The recording did not appear in the list of recordings saved on this device after an interruption.
- Upload all claims success but the recording is not in your web library.
- The extension crashes Chrome (rather than just failing gracefully).
- Any silent data loss.
File on the desktop app repo (seasalt-ai/seameet-app-desktop) with the extension version, the browser version, and if possible, a screenshot of the side panel.
Quick Reference
| Symptom | Try |
|---|---|
| Extension didn't record | Reload the tab, then retry |
| Recording missing after crash | Check the list of recordings saved on this device in the side panel |
| Upload failed | Click Upload on the row, or Upload all; it continues from the parts already uploaded |
| Not signed in, want to keep the recordings | Sign in to save all, or Download each one |
| Captions stopped | Click Retry captions in the transcript area |
| Storage warning at 500 MB | Sign in and Upload all, or Download and Delete |
| Meeting kept recording after end | Update to 1.9+ if you're not already |
Last updated: 2026-10-15
← Chapter 5: Sign In and Sync to the Web App | Chapter 7: Google Calendar Reminders and the Side Panel →
Published: