Created attachment 137151 [details] Capture SUMMARY git d239b67 Capture attached. - It didn't happen when I first started the Krita 5.0 alpha. It happened after I switched few times between Krita 4.3.3 and 5.0 alpha. - It starts to work again after rebooting PC. - I cannot ignore it. if I press 'Ignore' it just shows up again. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Forgot to mention the OS : Windows 10 x64
Are you really still using Krita 4.3.3? You don't mean 4.4.3?
> - It didn't happen when I first started the Krita 5.0 alpha. It happened > after I switched few times between Krita 4.3.3 and 5.0 alpha. It was between 4.4.3 and 5.0! Sorry that I mistyped.
Normally safe asserts aren't visible. You're using a testing package that was built by Dmitry for testing, not an official package.
Are you saying the portable krita from https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ is not official? I'm kinda confused.
The version of Krita used to report this is one built for you by Dmitry, not the official nightly build -- that has the safe asserts hidden. The c:\dev\env-7 in the message comes from Dmitry's build setup.
That's strange, because it obviously was the official nightly build that I got the safe assert. I did use the Dmitry's test build to test the smudge engine too though before I ran into this safe assert. Maybe those can affect each other? I wouldn't know. And you don't seem consider this a problem at all. I'm good with that too if you say so.
But I don't get it: the nightly builds are built HIDE_SAFE_ASSERTS=ON -- which means they cannot show those asserts. Could you please try the following: * clear away %LOCALAPPDATA%\krita.log * make sure you are starting the nightly build from the binary factory * if you get a safe assert message, please make a screenshot of that and append it: it should refer to a source file in a different location than in the screenshot you appended * and append the newly created %LOCALAPPDATGAQ%\krita.log to this bug report
setting this to needsinfo.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!