Closed knoppmyth closed 1 year ago
Hi @knoppmyth, I would guess this is related to musl, the arch C runtime. Perhaps you are running out of stack? musl defaults to an extremely small C stack which can cause issues. Though I think they've raised this a bit now.
libvips tries to raise the minimum stack size as it starts up, but it can't do this if libvips init happens after the first thread has been created. Importing libvips right at the start might help, or recoding your program in C could help.
Hello @jcupitt thanks for the information. I did have success running this the later part of last year. Of course Arch has been updated a lot since then... Unfortunately, I'm not proficient in C.
I've made a docker image to do my work.
I've searched the issues and not seeing an exact match to what I'm see.
I'm running the above with
It runs for a while but
after a little bit...
I'm running on a system with 32GB of RAM. I monitored memory usage and I'm not running out of memory. I'm running on Arch Linux in a venv. pyvips version is 2.2.1 libvips version is 8.14.2
Please let me know what other information I can provide.