mqudsi Posted April 2, 2018 Share Posted April 2, 2018 AD/AP should block all processing/rendering/etc threads when it is not the active window or when it is minimized. Active tasks (the type that would present a progress dialog like export/save/etc) should of course not be suspended, but there's no reason for AD to be rendering the canvas when it's in the background. Additionally, all tabs except the current tab should always be suspended. The CPU (not memory) profile of AD when open with a single tab active (and not "multiple documents mode" enabled) should be identical whether that tab is the only tab loaded in AD or one of a hundred. Quote NeoSmart Technologies Link to comment Share on other sites More sharing options...
mqudsi Posted April 3, 2018 Author Share Posted April 3, 2018 I suppose that means timer events should be classified into "fires in background" and "doesn't fire in background" with the default being the latter? Presumably that would address/workaround (without fixing) Quote NeoSmart Technologies Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.