Each time Launchy rescans, it adds about 50 MB to its footprint.. Often I find it sitting above 1.5GB and have to kill it.
Any clues as as to what is doing this?
Do you have locations in the Catalog that are refreshed often, such as temp folders?
How often is Launchy configured to rescan? I know you can choose a timing. I had the same issue and just chose to refresh manually, as most of the files I access are static.
After earlier reports of memory leaks, Josh said that Launchy wasn't designed to scan large numbers of files, and suggested something like 10,000 files as an upper limit. See:
You should also probably use the "latest beta" (2.6 beta 2), released in late 2010.
had a longer post about this, but sourceforge ate it. anyway, had a similar issue (+/- related to rescanning) where memory would grow, and i think it may be related to plugins.
try disabling them all. now memory grows, but my vastly smaller amts. other threads mentioned one specific plugin or another is responsible, but the plugin engine itself could be responsible. that maybe a good starting point for someone with the skillset to fix the bug.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.