Skip to content

Memory Compression 1.3.0

Latest

Choose a tag to compare

@M47E1 M47E1 released this 18 Oct 07:31

Memory Compression 1.3.0

Memory cleanup is now manual-only. Opening the app, logging in, or waiting for the preview retry timer does not clean RAM.

  • Optional Windows Memory Cleaner 3.0.8 integration, restricted to /StandbyListLowPriority.
  • No process working-set purge, full standby purge, or forced modified-page writes.
  • A separate optional installer verifies the official release file and Authenticode signature. The cleaner itself is not bundled.
  • Normal UAC confirmation is requested only for an explicit manual clean. The preview tool does not need administrator privileges.
  • Localhost page-close cleanup and its retry timer remain independent. Existing conservative process matching is retained.
  • Success requires a successful engine exit and corresponding success record, rather than an increase in the system-wide free-memory number.

Downloads

  • memory-compression-1.3.0-windows-portable.zip: Windows executable, browser extension, optional engine installer, and instructions. Extract before running.
  • memory-compression-1.3.0-windows-source.zip: clean source and build/test scripts.
  • checksums.txt: SHA-256 checksums for both ZIPs.

To add the optional cleaner, run Install-WindowsMemoryCleaner.ps1 from the portable folder and restart Memory Compression. It does not execute cleanup or install a service/startup task. If your organization blocks the script, use an approved environment; do not disable security protections.

Verification and limits

Local checks passed: 8 JavaScript tests, 91 controller assertions, 50 classification cases, 28 engine-policy assertions, and 26 WinForms runtime assertions. The freshly unpacked portable app started with manual-only defaults; the source ZIP compiled independently; the optional installer downloaded and verified its engine without executing it.

No local configuration, user paths, runtime journals, test output, browser profiles, or third-party executables are included. An additional browser run was not started under local memory pressure. This release does not promise that cache cleanup makes a computer faster; no second physical Windows machine or enterprise-policy setup was tested.