Re: Segmentation faults with remote mode
|
The remote segfaults are definitely network or cpu lag related. Since I'm running quisk in an ubuntu VM on my control laptop, sometimes it will struggle when plugged into my huge monitor and it's drawing a ton of pixels. This lag will crash the remote. Also when my daughter decides she wants to play minecraft while watching a 4k movie and the wife is using SMB over a VPN while on a work video conference... ?well?you get the picture.
I also found that although the remote was set-up to sample at 96khz bandwidth, the audio was garbled and unintelligible. Switching the audio card on the remote to 48khz fixed that and helped tremendously with the seg faults. I have been able to run for up to an hour without a crash. I'd definitely?like to get it back to 96khz or the full 192khz eventually, so I may dig into understanding the remote/control buffers at some point. I also may put a network switch in my garage eventually, even though the remote is 5ft from a ubiquity WAP.
-Eric WW4ET
On Thu, Jan 5, 2023 at 2:17 AM Gisle Vanem < gvanem@...> wrote: Not sure it's related, but one cause of crash on Windows, was this illegal ptr to free():
--- orig-quisk-4.2.15/quisk.c 2022-12-20 22:26:07
+++ quisk.c 2023-01-05 07:16:17
@@ -3101,7 +3101,7 @@
return NULL;
wisdom = fftw_export_wisdom_to_string();
pyBytes = PyByteArray_FromStringAndSize(wisdom, strlen(wisdom));
- free(wisdom);
+ fftw_free(wisdom);
return pyBytes;
}
(I hope does not massacre the above Markdown).
|
