Bug 447586

Summary: Kr 5.0.0 on macOS 12.1 opening a new canvas and loading images is unusually slow.
Product: [Applications] krita Reporter: Ek.artifist <ek.artifist>
Component: GeneralAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: minor CC: amy
Priority: NOR    
Version: 5.0.0   
Target Milestone: ---   
Platform: macOS (DMG)   
OS: macOS   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: attachment-606-0.html

Description Ek.artifist@gmail.com 2021-12-27 21:01:25 UTC
Krita 5.0.0 on macOS Monterey 12.1:

creating a new canvas is very slow and so is loading an image file.
Comment 1 amyspark 2022-01-03 22:48:03 UTC
This should be fixed as part of 446984. Can you check that it's fixed in the latest Krita Stable nightly build?

https://binary-factory.kde.org/job/Krita_Stable_MacOS_Build/
Comment 2 Ek.artifist@gmail.com 2022-01-05 18:36:34 UTC
Created attachment 145138 [details]
attachment-606-0.html

Hi Amy, sorry i was slow to respond. I just installed krita-nightly-428C799
on macOS 12.1.

Opening a new canvas took about 2 seconds, a big improvement, same as 4.4.8.

Also, importing an image to a layer too about 2 seconds, same as 4.4.8.

An improvement.

On Mon., Jan. 3, 2022, 2:48 p.m. amyspark, <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=447586
>
> amyspark <amy@amyspark.me> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |amy@amyspark.me
>              Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
>
> --- Comment #1 from amyspark <amy@amyspark.me> ---
> This should be fixed as part of 446984. Can you check that it's fixed in
> the
> latest Krita Stable nightly build?
>
> https://binary-factory.kde.org/job/Krita_Stable_MacOS_Build/
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 amyspark 2022-01-05 20:33:01 UTC

*** This bug has been marked as a duplicate of bug 446984 ***