-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEGV while transcoding #287
Comments
During configure we provide both STB and GraphicsMagick++.
Why then does the error message contain |
I checked and I did not find any code inconsistency. Do you by chance have a callstack of the crash? |
The issue is somewhere in the STB code, when I built with GraphicsMagick instead I don't have any issue at all. |
Thanks, that would be really helpful! |
I can't reproduce when build with debug flags however, when I do build with libasan I do get the following traceback
|
Ok this callstack is unrelated to image/cover handling, but it is about transcoding (we fork/exec to lauch ffmpeg). |
@epoupon Why are there two choices for image library, STB and GraphicsMagick++? Is one of them better than the other? Do they provide different functionality? |
STB eats far less memory, but I kept the other one for distribs that do not package it |
I've got a similar SEGV without subsonic transcoding and without STB involved:
Maybe it was local transcoding, not sure. |
Thanks for the info. Well it would confirm this is not likely to be related to the image library backend. You can set the log level to |
Log level is set to:
|
You can remove |
No additional details w/out
|
And indeed, GraphicsMagick does set up its own signal handler and intercepts the crash (see InitializeMagickSignalHandlers at http://hg.code.sf.net/p/graphicsmagick/code/file/tip/magick/magick.c#l1055), since GM is used by the wt library, this explains the misleading message you got. |
I can confirm the fix on my side! thank you very much! |
Settings are:

Version: 3.34.0
OS: FreeBSD 13.1
The text was updated successfully, but these errors were encountered: