Adam Hupp
Adam Hupp
Yes, ^^ that's true. Too many similarly named packages unfortunately.
This is huge, thank you! Apology for the delay I thought I'd commented earlier but guess not. I'll look this over soon; I didn't quite understand how bad the binary...
Thanks for the details. This PR adds build setup for shipping binaries, I'll look it over in detail soon: https://github.com/ahupp/python-magic/pull/294 On Mon, Sep 4, 2023, 10:08 PM jspraul ***@***.***> wrote:...
Based on the error message it looks like a memory allocation error. Does this happen consistently for one file, or only after running for a while?
Are you creating a new instance of magic.Magic() for each file, or creating one and re-using it?
Can you share the file that seems to trigger this? Which version of libmagic are you using?
> appears to happen at the same file. Are you able to share the input file that triggers it? What version of libmagic are you using?
If you were running into this error it looks like you do have libmagic installed, that's what produces the error.
Thanks for the repo; this is definitely due to the older version of libmagic shipped with python-magic-bin. Just another case where the binaries situation causes trouble.
I get the segfault even when (I think?) I've requested the lavapipe software renderer, so I suspect this is at least partly a regular bug rather than an unimplemented feature:...