Memory Leak: Launchy 2.5.0 on WIndows 7

Help
2013-06-02
2013-06-19
  • RobertMarkBram

    RobertMarkBram - 2013-06-02

    Hi All,

    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?

    Rob
    :)

     
  • Thomas

    Thomas - 2013-06-03

    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.

     
  • RobertMarkBram

    RobertMarkBram - 2013-06-09

    Hmm...

    • I have only 1745 entries
    • No temp directory is scanned
    • Auto-update set to 10 minutes. I am turning auto-update OFF.
    • I remember months ago swapping back to v2.5.0 because I noticed 2.6 beta 2 had this same memory issue.
     
  • traycerb

    traycerb - 2013-06-19

    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.

     
    Last edit: traycerb 2013-06-19

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks