You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Restarting the application restores TX functionality — but only temporarily.
Additional observations
The log file at ~/.local/state/trackaudio/trackaudio.log continues to record PTT input events during the broken state.
(See around 2025-04-24 21:26:37.145 in the attached log.)
I'm not sure if this problem also existed in previous versions.
I recently switched from Windows to Linux, and my only session on version 1.3.1 was likely too short for the issue to occur.
Let me know if I can provide more logs or test a debug build.
The text was updated successfully, but these errors were encountered:
Have you ever had this issue on Windows, or purely on Manjaro? Sounds like there might be a memory leak on this platform and I know where this could come from.
No, windows worked (and works) fine. A memory leak might be the case, although the memory footprint only rises by a few hundred megabytes. Do you need some more info?
Uh oh!
There was an error while loading. Please reload this page.
TX becomes unresponsive after ~2h of use, 100% CPU on one core
I'm using TrackAudio 1.3.3 on Manjaro Linux (kernel 6.14), and I'm encountering an issue where TX becomes unresponsive after extended use (~2 hours).
Symptoms
htop
shows one CPU core at 100% usage caused by the TrackAudio processAffected versions
This behavior occurs with both:
trackaudio-bin
AUR packageTemporary workaround
Restarting the application restores TX functionality — but only temporarily.
Additional observations
The log file at
~/.local/state/trackaudio/trackaudio.log
continues to record PTT input events during the broken state.
(See around
2025-04-24 21:26:37.145
in the attached log.)📎 trackaudio.log
Version history
I'm not sure if this problem also existed in previous versions.
I recently switched from Windows to Linux, and my only session on version 1.3.1 was likely too short for the issue to occur.
Let me know if I can provide more logs or test a debug build.
The text was updated successfully, but these errors were encountered: