Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mac 1.3 beta performance issues #3592

Closed
ThomasFOG opened this issue Nov 11, 2022 · 7 comments
Closed

mac 1.3 beta performance issues #3592

ThomasFOG opened this issue Nov 11, 2022 · 7 comments

Comments

@ThomasFOG
Copy link

Hello!

It seems that the current 1.3 beta has memory/performances leaks. The program runs fine, but after some time of usage (varying, but more than an hour of work) it becomes increasingly slow to operate down to unusable.

This problem is not present on 1.2.4 (and as far as we can tell, it was present in all 1.3 betas and never in the 1.2 branch).

Thanks for aseprite, it's likely the tool that has the most enhanced our workflow.

Cheers!

Aseprite and System version

  • Aseprite version: 1.3 beta 21 x86 (dmg from Humble)
  • System: macOS, 12.1, x64
@Gasparoken
Copy link
Member

Thanks for your report! We'll look into it.

@Gasparoken
Copy link
Member

Taking some notes on a particular action: opening and closing the Preferences dialog several times consumes more and more VM: IOSurface memory.
Screenshot 2022-11-30 at 18 49 59
OS: MacOS Ventura
Aseprite 1.3beta21-x64

@Gasparoken
Copy link
Member

As a workaround until this is resolved: uncheck Edit > Preferences > Experimental > UI with multiple windows

@ThomasFOG
Copy link
Author

We tested the suggested workaround over a workday and it seems like that was it!

@Gasparoken Gasparoken added wip and removed wip labels Dec 3, 2022
@Gasparoken Gasparoken removed the wip label Dec 13, 2022
@dacap dacap self-assigned this Feb 23, 2023
@dacap dacap added the wip label Feb 23, 2023
@dacap
Copy link
Member

dacap commented Feb 23, 2023

This is issue is almost fixed (still NSWindow objects are not deallocated, but it will need further debugging).

More info in the commit description: dacap/laf@6693518

@dacap dacap removed the wip label Feb 23, 2023
@dacap dacap modified the milestones: v1.3, v1.3.0 Feb 23, 2023
@briankendall
Copy link

In case it helps, I can trigger the bug quickly by painting a couple of paint strokes and then repeatedly undoing them and redoing them. Basically I just quickly mash Cmd+Z Cmd+Z Cmd+Z Cmd+Shift+Z Cmd+Shift+Z Cmd+Shift+Z over and over again very quickly.

After I've done that around 30 or 40 times the app will be very laggy when I try to paint anything.

@ThomasFOG
Copy link
Author

On our end, we haven't been noticing performance issues since the main release of 1.3. (Not denying the previous comment, just saying that one of the scenarios seems clear.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants