RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

slow startup from too many plug-ins installed

This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

4 of 4 messages available
Toggle history

Please log in to manage your subscriptions.
slow startup from too many plug-ins installed Dan Kronstadt 21 Dec 00:37
  slow startup from too many plug-ins installed Frank Gore 21 Dec 01:22
  slow startup from too many plug-ins installed Steve Kinney 21 Dec 04:43
slow startup from too many plug-ins installed Dan Kronstadt 21 Dec 16:04
Dan Kronstadt
2011-12-21 00:37:33 UTC (about 13 years ago)

slow startup from too many plug-ins installed

Hello, all. I'm new to Gimp - running on Windows. I think I took the defaults on installation. My problem is slow startup - and I think the problem is the 170 modules I have in the plug-ins directory. I moved them all somewhere else, and Gimp started up really fast - but I could not, for example, even open a jpg image. I think the only option was a native Gimp file.

So - any suggestions on getting a more reasonable number of plug-ins? What's a good startup set? Or - is 170 normal, and I have some other problem that is making startup of these modules so slow?

Thanks. Dan

Frank Gore
2011-12-21 01:22:33 UTC (about 13 years ago)

slow startup from too many plug-ins installed

On Tue, Dec 20, 2011 at 7:37 PM, Dan Kronstadt wrote:

So - any suggestions on getting a more reasonable number of plug-ins? What's a good startup set? Or - is 170 normal, and I have some other problem that is making startup of these modules so slow?

Most likely a specific plugin is causing the slowdown. But trying each plugin one at a time will take forever to pin it down. You could try the "half and half" method. Leave only half the plugins in the directory, then try starting up Gimp. If it starts up normally, you know the problematic plugin is one of the ones you removed. If it starts up slowly, then you know it's one of the ones that was loaded. So either remove half the plugins that are left (if it was slow starting) or remove all plugins and add back half the ones that weren't originally loaded (if it was starting fine), and try again.

Rinse and repeat until you can figure out which plugin(s) was causing the slowdown in startup time.

-- Frank Gore
www.ProjectPontiac.com

Steve Kinney
2011-12-21 04:43:04 UTC (about 13 years ago)

slow startup from too many plug-ins installed

On 12/20/2011 07:37 PM, Dan Kronstadt wrote:

Hello, all. I'm new to Gimp - running on Windows. I think I took the defaults on installation. My problem is slow startup - and I think the problem is the 170 modules I have in the plug-ins directory. I moved them all somewhere else, and Gimp started up really fast - but I could not, for example, even open a jpg image. I think the only option was a native Gimp file.

Hey Dan,

I ran into a similar problem a couple of years ago on a Windows XP installation. It's been a while but from digging around in the forums I think I recognize this as what fixed it for me: Find and delete ~/home/.fonts-cache1 (Or to be on the safe side, RENAME the thing, so you can put it back as it was if something breaks!) IIRC the problem was some corrupted files in the said cache.

I have been using a large number of optional plugins in addition to all the normal ones, and a large set of optional and user-made brushes for a long time on both MS and Linux boxes, including some with VERY low resources. The time it takes to scan plugins, brushes, etc. when starting has never been more than ten seconds or so. The "five minutes or more to start" issue I ran into was a one time thing solved by removing the above mentioned cache. Hopefully that or something similar will solve your problem - removing plugins means removing important components, unless you can identify some that you literally never use.

HTH,

Steve

Dan Kronstadt
2011-12-21 16:04:50 UTC (about 13 years ago)

slow startup from too many plug-ins installed

Well, thanks, Frank and Steve for the suggestions. My problem is fixed, altho I am not sure whether it GOT fixed while trying Frank's suggestion - or I never really had a problem in the first place.

I understand (now, better) that Gimp caches a lot of startup info the first time it starts, or whenever things change - I thought of that mainly for fonts - but I guess it does it for plug-ins as well. So, as I was testing with half my plug-ins, it started fairly slow, then a restart with the same set was quite fast. So I tried the OTHER half - and that was, again, fairly slow the first time, then quite fast the second. Tried it again with all the plug-ins - same result: slow, then fast on a restart. And fast again this morning.

But it does seem like these tests were NEVER as slow as when I tested a few days ago. So, I insist on blaming a corrupt cache, that got cleaned up in some of my testing! :-)

Anyway - thanks again - now I can start learning Gimp. Dan