You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If rlottie is compiled using MinGW 9.2.0 then the application will hang (seemingly forever) on shutdown if either render() or renderSync() has been called at least one.
This problem does not occur when compiled using MSVC but unfortunately I need to use MinGW for my release builds so that's not a solution for me.
I have also not seen the issue on any of the other operating systems that I've built rlottie on (macOS, Linux, FreeBSD, NetBSD and OpenBSD).
This issue is present on the master branch with the latest commit 8756269.
I have compiled as shared library/DLL and apart from the hang on shutdown, everything seems to work fine with correct rendering and equivalent performance compared to other platforms.
Many thanks in advance!
The text was updated successfully, but these errors were encountered:
One additional comment, I just managed to get the MinGW build to work by disabling the threading support using the LOTTIE_THREAD option.
After doing this the application shuts down correctly.
So the issue is definitely related to threading somehow.
Hi!
If rlottie is compiled using MinGW 9.2.0 then the application will hang (seemingly forever) on shutdown if either render() or renderSync() has been called at least one.
This problem does not occur when compiled using MSVC but unfortunately I need to use MinGW for my release builds so that's not a solution for me.
I have also not seen the issue on any of the other operating systems that I've built rlottie on (macOS, Linux, FreeBSD, NetBSD and OpenBSD).
This issue is present on the master branch with the latest commit 8756269.
I have compiled as shared library/DLL and apart from the hang on shutdown, everything seems to work fine with correct rendering and equivalent performance compared to other platforms.
Many thanks in advance!
The text was updated successfully, but these errors were encountered: