NVIDIA Geforce 3060 Laptop insufficient GPU memory - unable to start recording
P
Philipp Schweiger
I am getting insufficient GPU memory error when starting a session on hedy Windows with 16 GB RAM, Ryzen 5000 and a Geforce RTX 3060 Laptop. Is that normal behaviour? Also a few seconds later I am getting "Unable to start recording. Please try again..."
I attempted to start Hedy and initiate a session, but it failed as I mentioned. Then, I reinstalled Hedy, and it worked. However, when I rebooted my PC and tried to start Hedy again and initiate a session, I received the "session start failed" report once more. I'm not sure what the problem is with my installation. It just doesn't work, even after I tried uninstalling and reinstalling several times. Is there anything that could be synced (db etc.) that inhibits hedy from working?
Julian Pscheid
The second error points to Hedy not being able to get write access to the database file. On Windows, sometimes the document folder is synced through OneDrive, which can lock the file temporarily. Do you know if OneDrive sync is enabled on your machine?
P
Philipp Schweiger
Julian Pscheid we already had that discussion in another thread. Not synced except with hedy application cloud sync. Is there any way to completely reset hedy database, online, local etc. I'm out of ideas how to get hedy back to work. As said, I only deleted the audio files of done sessions and since then hedy first threw the error can't write when starting. Reinstalled. Then that message was gone. Wanted to start a session, got this error message. Reinstalled again. Then session started without the red error (orange was still persistent). Restarted. Wanted to start the session for an important meeting, throws red error again... I need a completely clean slate to hopefully make this work again. Is there any option to completely reset everything except my account login?
Julian Pscheid
Philipp Schweiger Yes, I recalled the other conversation after sending my note. Thanks for the details. The issue started when the audio files were deleted, which likely left the local database in a bad state. Let's do a clean reset without losing anything permanently.
While Hedy is fully closed (check Task Manager too):
- Open Documents\Hedy\
- Rename these files (if they exist):
-
hedy_sessions.db
→ hedy_sessions.db.bak
-
hedy_sessions.db-wal
→ hedy_sessions.db-wal.bak
-
hedy_sessions.db-shm
→ hedy_sessions.db-shm.bak
- Start Hedy
This will force Hedy to create a fresh database. Since you use Hedy cloud sync, your session history should re-sync automatically (minus the audio files you already deleted).
If that works, you can delete the
.bak
files later. If it doesn't, rename them back and we'll dig deeper.Regarding the "No compatible GPU detected" warning (the orange banner): that's a separate issue we're investigating. It won't stop sessions from working, it just means transcription runs on CPU which is slower.
Could you also email me the file at this location? That would help us diagnose the GPU issue with your RTX 3060:
%LOCALAPPDATA%\Hedy\runtime_events.log
P
Philipp Schweiger
Julian Pscheid This has not worked. It still gives me the red error: Unable to start session recording. Are there any other logs that I can send you or I can look into to fix the problem? Also I have tried it without cloud sync and it still doesn't work.
Funny enough, after new install, I installed 3.0.5, session starting (GPU warning persists) works. As soon as I close the application and start it again or restart the laptop, session recording gives me the red error again.
Are there any registry files that I could clean up, any cloud data to delete (there's nothing important on there), anything to get my account and hedy setup to a state that is completely untouched?
Julian Pscheid
Hi Philipp Schweiger, that's strange. I thought we were pretty consistent in detecting the correct GPU at this point. Could I get you to try the latest version?
P
Philipp Schweiger
Julian Pscheid I've just updated to the newest version 3.0.5. The problem is still persistent. I've sent an email with the log file.
Julian Pscheid
Philipp Schweiger Sorry to hear about that. Let's continue the conversation on email.