| Summary: | Random crashes on Mac | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Yu-Hsuan Lai <raincolee> |
| Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED LATER | ||
| Severity: | normal | CC: | ghevan, halla |
| Priority: | NOR | ||
| Version: | nightly build (please specify the git hash!) | ||
| Target Milestone: | --- | ||
| Platform: | macOS (DMG) | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | system.log is the crash log shown by the OS. | ||
|
Description
Yu-Hsuan Lai
2020-04-07 10:08:51 UTC
The crash happens deep inside Qt, where it tries to create or draw a window. I see you have a mac with a radeon gpu. If you disable canvas acceleration, do the crashes go away? (In reply to Boudewijn Rempt from comment #1) > The crash happens deep inside Qt, where it tries to create or draw a window. > I see you have a mac with a radeon gpu. If you disable canvas acceleration, > do the crashes go away? Ok, I disabled it and will keep using for a while. Strangely, after I disabled canvas acceleration, the UI actually feels MUCH faster (especially when I zoom the canvas). Is it a known issue? Yes, unfortunately Apple ships really bad opengl drivers. They want everyone to use Metal, but that's proprietary stuff, which we don't want to use. Until there's a good opengl to metal translation library, we'll have problems with macOS. It's one reason we haven't put Krita in the Apple store. The CPU-based canvas has its own problems, and it doesn't support some features, like tiling the canvas. (In reply to Boudewijn Rempt from comment #3) > Yes, unfortunately Apple ships really bad opengl drivers. They want everyone > to use Metal, but that's proprietary stuff, which we don't want to use. > Until there's a good opengl to metal translation library, we'll have > problems with macOS. It's one reason we haven't put Krita in the Apple > store. The CPU-based canvas has its own problems, and it doesn't support > some features, like tiling the canvas. Ok, I understand that Mac has bad support for OpenGL. I've heard the same issue from Blender's community too. It's rather off-topic, but do you think it's possible to switch to Vulkan and MoltenVK, which are both open protocols? Again I understand it's not trivial work and not Krita devteams' priority. Back to the original issue, I haven't experienced another crash so far, but I think it's better to wait for several days before we close the case. (And perhaps the canvas acceleration should be disabled by default on Mac?) We're hoping that Angle (which we use on Windows) will soon see its Metal backend released -- then our problems should be much less. Porting to Vulkan isn't planned at this point. (In reply to Boudewijn Rempt from comment #5) > We're hoping that Angle (which we use on Windows) will soon see its Metal > backend released -- then our problems should be much less. Porting to Vulkan > isn't planned at this point. Got it. Another issue (anti-issue?) I've noticed is that even you said tilting canvas isn't supported, I can still rotate my canvas with canvas acceleration disabled. Or tilting and rotating are two different things? I was talking about tiling, not tilting. Tiling shows your image repeated horizontally and vertically -- it's very handy when painting seamless textures. (In reply to Boudewijn Rempt from comment #7) > I was talking about tiling, not tilting. Tiling shows your image repeated > horizontally and vertically -- it's very handy when painting seamless > textures. Oh okay, I misread lol. Thanks for your patience to silly me. Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. I kept using it for several hours and no crash so far. But technically this bug still presents right? Turning off canvas acceleration seems like a workaround. Do you have a WONT-FIX-YET status? That would be resolved-later -- but I'll just keep the bug open for now. Though resolved-upstream might also be the case, given it happens in Qt's code. Do take note that current master is extremely laggy and prone to crashes. Fo work I suggest using the 4.3 branch, and keep master for testing. Even on my macbook pro, current git master can be slow and unusable in some cases. won't-fix-yet is resolved-later :-) |