sashwilko

PDN very slow to start

Recommended Posts

sashwilko    358

Recently after the Windows 10  update (1607) OS Build 14393. 187. Paint.net (4.0.12) is taking a long time to allow me to either open an image / create new or just open a fresh 800x600 canvas. The below image with the "not responding" text in the upper right, is what I get for around Three to Five minutes.
aewnpe.jpg

 

Below is text copied from the diagnostics within pdn. Hope this can help solve the issue. Thanks :)
----------------------------------------------------------------------------------------------------------------------------
Application    paint.net 4.0.12 (Final 4.12.6099.39434)
Build Date    12 September 2016
    
Hardware accelerated rendering (GPU)    True
Animations    True
DPI    96.00 (1.00x scale)
Language    en-GB
    
OS    Windows 10 (10.0.14393.0)
.NET Runtime    4.0.30319.42000
Physical Memory    8,114 MB
    
CPU    Intel(R) Core(TM) i3-5157U CPU @ 2.50GHz
    Architecture    x64 (64-bit)
    Process Mode    64-bit
    Speed    ~2494 MHz
    Cores / Threads    2 / 4
    Features    DEP, SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, XSAVE
    
Video Card    Intel(R) Iris(TM) Graphics 6100
    Dedicated Video RAM    128 MB
    Dedicated System RAM    0 MB
    Shared System RAM    4,057 MB
    Vendor ID    0x8086
    Device ID    0x162B
    Subsystem ID    0x8093103C
    Revision    9
    LUID    0x0000C75B
    Flags    None
    Outputs    1
    
Video Card    Microsoft Basic Render Driver
    Dedicated Video RAM    0 MB
    Dedicated System RAM    0 MB
    Shared System RAM    4,057 MB
    Vendor ID    0x1414
    Device ID    0x008C
    Subsystem ID    0x00000000
    Revision    0
    LUID    0x0000CA13
    Flags    Software
    Outputs    0

Edited by sashwilko

Share this post


Link to post
Share on other sites
BoltBait    1,225

Try this: reinstall paint.net

 

This will force Windows to recompile the application for your system.

  • Upvote 1

Share this post


Link to post
Share on other sites
sashwilko    358
10 minutes ago, BoltBait said:

Try this: reinstall paint.net

 

This will force Windows to recompile the application for your system.

Uninstal first or reinstall over current build ?  And would I need to remove all plugin's ?

Edited by sashwilko

Share this post


Link to post
Share on other sites
BoltBait    1,225

It works out to be the same.  I recommend, just running the latest installer (download from here.) 

Share this post


Link to post
Share on other sites
Rick Brewster    813

What BB said :) It sounds like the usual "jiggle the handle" troubleshooting stuff, but in this case it actually applies.

 

Technical explanation: OS upgrade causes the NGEN cache to be emptied. This contains .NET assemblies (DLLs) that have been precompiled so that they don't have to be JITted. Paint.NET leans on this heavily to improve its startup performance; on my system it's the difference between 10+ second startup time versus <1 second. Windows will automatically rebuild the NGEN cache ... eventually. There's also a command you can run to force this to happen (ngen /executeQueuedWorkItems, I think?). Reinstalling Paint.NET is probably the easiest way to get this done though.

  • Upvote 1

Share this post


Link to post
Share on other sites
sashwilko    358

Reinstalling has made some difference, now down to less than a minute before I can use pdn, a lot better than 3 - 5 minutes for sure. I will also have to follow the advice of EER and remove some of my lesser used plugin's. Perhaps storing the less used in another folder elsewhere and if needed copy / paste. Thanks all for the help and advice :)

Share this post


Link to post
Share on other sites
Rick Brewster    813

A quick way to determine the maximum possible improvement: quit Paint.NET, rename Effects to Effects.bak, FileTypes to FileTypes.bak, and Shapes to Shapes.bak, and then start Paint.NET again. (or replace ".bak" with whatever you want) It will then start up with zero plugins.

  • Upvote 1

Share this post


Link to post
Share on other sites
sashwilko    358
5 minutes ago, Rick Brewster said:

A quick way to determine the maximum possible improvement: quit Paint.NET, rename Effects to Effects.bak, FileTypes to FileTypes.bak, and Shapes to Shapes.bak, and then start Paint.NET again. (or replace ".bak" with whatever you want) It will then start up with zero plugins.

I  know from first install with no plugin's installed pdn started up very fast when I first got my laptop, I will try your suggestion too and see what difference it makes. Thanks Rick :)

Share this post


Link to post
Share on other sites
wreckage    1

I would just like to mention that I've been a 'victim' of very long opening times (yes, the three-to-five minutes as mentioned above), and because of this post I found that my Effects folder contained two .txt files and a .pdn.   When they were deleted opening times returned to normal.   I've been frustrated by that for months!    Glad to say it's now fixed.

 Looks like it's a no-no to have any foreign file-types in the Effects folder.

 

It would seem that I was incorrect in my above 'resolution'.  (I neglected to rename the Effects folder back after changing it).  However, when the Effects folder is renamed, Paint.net opens quickly and as expected so the problem does lie with one or more DLL files.
 I'm starting to trouble-shoot by renaming the oldest effects and seeing what happens.  So far I've renamed all DLLs older than 2014 and the program (right-clicking on a file and selecting Open With Paint.net) now opens in around 30 seconds.

 With the Effects folder renamed the program and image open almost instantly, so the issue is definitely caused by one-or-more Effects.

Hopefully, I'll have the time to narrow this down to the offending culprit.

My currently-installed Plugins are as follows:

sb-plugins

TechnoRobbo's

pyrochild

dpyplugins

BoltBait

shadow effect1_3.

and 'feather'

 I'll let you know if I find the culprit(s)

 

 

 

Edited by wreckage
Incorrect information

Share this post


Link to post
Share on other sites
wreckage    1

OK... disregard the entire above post.

  I kept thinking that the issue was resolved but it is not.   Paint.net on my computer takes 5 minutes to open an image THE FIRST TIME it is executed.

If I wait the 5 minutes (during which time the computer is entirely unresponsive, although keystrokes are saved and executed after the 5 minute waiting period), then close Paint.net and then open the same, or a different image, it fires right up as it should.

  This issue is deeper than I initially thought and must relate more to other software/drivers on the computer than to Paint.net.   I'll have to trouble-shoot this another day because my brain can't wrap around the problem now.  Some weeks ago I entirely uninstalled Paint.net and removed its registry entries, re-booted and re-installed it only to suffer the identical issue.. Ho hum.  If anybody has any hints in the meantime, feel free to comment.

Cheers.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now