Skip to content

[feedback] memory usage and lznt1 support #628

Open
Open
[feedback] memory usage and lznt1 support#628

Description

@SeriousConcept1134
SeriousConcept1134
opened on May 12, 2026

I've tried CompactGUI for the first time today, and I really like almost everything about it except a couple of things:

  • Why is it taking up anywhere from 300-500MB in RAM when it's just idling in the background? For comparison, something like CompactRS takes just ~21MB while actively performing compression operations.
  • It would be great if CompactGUI supported evaluating and directly recompressing directories which are already compressed with LZNT1, rather than just throwing an error saying they're unsupported and refusing to even open them. This is a big limitation.

Thanks!

Activity

  1. SeriousConcept1134 commented on May 19, 2026

    @SeriousConcept1134
    SeriousConcept1134
    on May 19, 2026
    Author

    No response?

  2. Iridium-IO commented on Aug 25, 2026

    @Iridium-IO
    Iridium-IO
    on Aug 25, 2026
    Member

    Sorry for the late reply - not sure why it's taking up so much RAM on your system, there might be a memory leak that I can't find on my end. I'll keep looking as I'm currently back to make some improvements in the program.

    As for LZNT1 support, it's kind of cursed when combined with the XPRESS options, and enough people have issues with filesystem errors caused by Windows' handling of compression (and I still don't know what the cause is!) that I flatly did not want to have to deal with the bugginess that can come with it - hence the hard block.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions