This also applies for possible threads created by Krita ( may confirm).
You will note that most command samples below contain these two lines, but the truth is you only need to run env.bat once for each CMD window. I think G'MIC-Qt also creates threads ( may confirm), so it may be necessary to apply the same kind of hack for those threads too. Every time you want to build or run your home-grown Krita, open the CMD window, change to the C:krita-dev folder and run the env.bat file: cd /d C:krita-dev env.bat.
Where we try forcing the stack size of a new thread to be 8 Mo (which is actually the default size for Linux systems, where everything runs fine :) ).īut that hack is done for the moment only for threads that are created by the G'MIC interpreter itself, not threads that could be created by the G'MIC-Qt plug-in or by Krita. That particularly why we have this hack in file gmic.cpp: Your log suggests it could be related (I see multiple threads trying to run there). Īfter years of investigation, we found out it was due to the fact that on MacOS, the default stack size allocated for a new thread is ridiculously low (512 KB by default), and that it was not enough for the G'MIC commands running with multi-threading. We don't have a Mac, so we'll have a hard time being useful here.Īnyway, I remember that for years, we got frequent G'MIC crashes in the past on MacOS, with frequent reports by.
0 kommentar(er)
