Summary
Just crashed out of nowhere with the following error:
Steps to reproduce
N/A
EarTrumpet version
3.3.1
Windows version
10.0.19045.6456
Additional information
No response
Opened by vertigo220 · 2 months ago
Just crashed out of nowhere with the following error:
N/A
3.3.1
10.0.19045.6456
No response
sorry about that! that error is a native crash so i need a bit more context to track it down. could you zip %APPDATA%\BetterTrumpet\logs and drop it here (or use settings > about > export diagnostics right after it happens)? also, does it happen when the flyout is open, after waking from sleep, or when a device connects/disconnects? 3.4.0 is out too, worth a try in case it's related to the stuff i fixed: github.com/xammen/…/v3.4.0
[!NOTE] 🤖 Claude Opus 5.5 responding on behalf of xammen
3.5.0 fixed a crash source in device handling: when a device disconnected and came back, BetterTrumpet kept stale audio callbacks around. 3.5.1 also fixes a memory leak on the same path.
Is it still crashing for you on 3.5.0 or 3.5.1? If it is, please attach the newest log from %APPDATA%\BetterTrumpet\logs (or Settings → About → export diagnostics). That's what's needed to track it down.
Sign in to comment.
Just had this happen again, same error.
It doesn't look like there's anything personal in the logs, but there's too much to sift through to be sure, so I'd rather send to you another way that's private/secure. Though I'm hopeful 3.4 fixes the issue. Looking at the logs from before vs after, BT seemed to be constantly logging info entries "MediaSessionService: No playing session found..." during times I was active, all hours, all the time, which I suspect may have been due to the CPU issue you fixed and may have been causing a buffer overflow or something. So for now, I figure just give it some time and we'll see if it crashes again. It would happen probably at least once a week (probably more often except I'd go a while without noticing and therefore without it running), so should know within a couple weeks.
The version before the update 12 hours ago was crashing a lot. Sorry I couldn't get a screenshot of the error. It would produce constant error dialogue boxes for a minute and then finally stop
Crashed again on 3.5.0. Will try 3.5.1. As mentioned, logs are too large to check for personal data, so don't want to upload here.