I figured out what the issue below was caused by. Following on what IOhannes said it turned out there were too many opened files. To play files with the Else player~ object I was banging open a file each time it played. I guess it doesn't close the file after playing and I only had to bang the player~ object rather than the open command again. It would be nice if possible to print out a message to the console saying the file is already open to avoid such crashes . Anyway all is good now. Thanks for all the suggestions of what may be causing the issue
On 26/11/2025 21:06, Jim Ruxton wrote:
> I am using Pd 0.56.0 (Linux/amd64 - single precision) version of Pure Data
> on Ubuntu 24.04 and having a strange issue I'm having trouble tracking
> down. Wondering if anyone has come across this issue and found a solution.
> I have a patch that I am working on and after working on it for a while I
> can no longer save it . If I open that patch, make a quick change and save
> it, that works fine. After editing it for a while doing simple things like
> adding comments I can go to the file menu and save it, though it appears to
> work it doesn't actually save the file. The way I know it hasn't saved the
> file is if I then go to close the file , the prompt comes up asking if I
> want to save the file even though I just did save it. Also at that point I
> can't quit the program. It again asks if I want to save the program and I
> say yes but it doesn't quit. I then quit it in the console with cntrl c.
> And when reopening see that it hasn't saved my changes. The patch is
> working fine before and after I try to save and close it. Except there is a
> strange anomaly which is that I am playing short audio wav files using Else
> player and each time it goes to play the file there is a message in the
> console saying it can't find the file. Even though it plays the file it
> says it can't find. I don't have other instances of PD open or other panels
> that would prevent me from closing PD. It is a very strange issue I've
> never seen but it's driving me a bit bonkers as it appears pretty random
> when it decides it can no longer be saved. Any thoughts on what could be
> causing this strangeness?
>
my guess would be that your Pd process has run out of file-handles.
to check, get the PID of the pd process ("ps aux | grep -w pd"), and
then use `lsof -p $PID`, or simply "ls -lha /proc/$PID/fd".
to see the allowed number of simultaneously open files, use "prlimit -p
$PID", or simply "cat /proc/$PID/limits".
most likely a bug in some external, that opens files but doesn't close
them (i would have expected this to pop up earlier/more often, if it was
a problem in Pd itself)
gamdsr
IOhannes