Very long GP exit time, only on Windows

Gig Performer on Windows
1

Just fyi, there’s a huge difference in the time it takes GP to release its memory on exit, between the Windows and macOS versions. This is with my rather large work-in-progress .gig file, loaded on Windows: it currently contains a 23-song setlist, 52 rackspaces with Arturia, NI, BlueArp and Kilohearts plugins, several complex local rackspace scripts, and an OSC connection to my iPad.

As seen in Windows Task Manager, it takes about 2 minutes and 11 seconds for the memory used to decrease from about 10.35 GB to 0 and then for the application to finally quit. On the Mac this only takes 2-8 seconds. Here are the numbers:

image
image401×332 31 KB

Note that SAVING the gig file only takes a few seconds. Here’s GP’s footprint on first loading the instance and the .gig file:

image

2

Mine take crazy long to release ram (over 10 minutes, I think), probably because I have (and use) a lot of ram.

But, it’s a non-issue. Whenever I close out GP, I just go into the Task Manager and close out GP. Then it just take about 10 second for the memory used by GP go down to under 10%, at which time I feel comfortable closing down the laptop.

[Before I used the method, I used to get error messages when I shut down the laptop. As long as I terminate the GP process in the Task Manager first, Windows closes smoothly, without any error messages.]