PM using a lot of memory when AP Custom features turned on

[pvernon69]

I am using PM 4.6.8 with Windows XP SP3. When I start PM with out AP custom features enabled PM starts up very quickly and then when I enable AP custom features the database loads very quickly and according to Windows Task Manager PM is using around 69,000k. If I do not disable AP custom features before I shut PM down and restart it it takes about 8 minutes to load and according to task manager it is using 519,000k. I have 3gb of ram but photoshop barely runs with this scenario. If I try to abort the custom functions from loading it still takes the 8 minutes and then says that they can't be run. Is there anything I can do besides remember to disable AP custom functions before I shut PM down?

[Kirk Baker]

I am using PM 4.6.8 with Windows XP SP3. When I start PM with out AP custom features enabled PM starts up very quickly and then when I enable AP custom features the database loads very quickly and according to Windows Task Manager PM is using around 69,000k. If I do not disable AP custom features before I shut PM down and restart it it takes about 8 minutes to load and according to task manager it is using 519,000k. I have 3gb of ram but photoshop barely runs with this scenario. If I try to abort the custom functions from loading it still takes the 8 minutes and then says that they can't be run. Is there anything I can do besides remember to disable AP custom functions before I shut PM down?

No.  When AP tasked us to build in those features, we never expected their database to get so large.  I think the feature is fairly unusable at this point.  It needs to have a database backend and needs to be re-written.

We just don't have the time right now.

-Kirk

[Jersey Tom]

I, too, have been experiencing the very long launch time of PM when using the AP Custom Features sub-program on my well-equipped Windows XP laptop.  It drove me nuts waiting for the program to launch.  I tried "pvernon69's" method of disabling the feature before launch and then enabling once launched and it works like a charm. I'll just have to remember to turn it off when I shut down.  Thanks for this useful tip.