[GH-ISSUE #5883] [bug]: Desktop app has huge memory hog in Windows #2315

New issue

Open

opened 2026-03-16 23:56:00 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 23:56:00 +03:00

Owner

Originally created by @francescodedomenico on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5883

Originally assigned to: @CuriousCorrelation on GitHub.

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Desktop App

Browser

Other (specify in additional info)

Operating System

Windows

Bug Description

What happened?

Hoppscotch Desktop app on Windows 11 has an huge resources consumption compared to the portable version.

Screenshot of the desktop app during bootstrap

Screenshot of the desktop app during bootstrap

The application won't start unless there is enough free RAM available, WebView2 runtime inflates up to 6GB during startup process. If not enough RAM is available the application hangs showing the spinnig wheel rotating in the main window.

The issue seems to be related to the handling of the Requests Collection , opening a portable version of Hoppscotch without any environment or requests opens almost instantly and has WebView2 runtime memory footprint of around 400MB, after reimporting my collections and restarting the portable version the Installed Desktop version behavior and memory consumption replicates.

Launching an HTTP GET request with a 3.43 json payload causes the consumed memory to have a 2x consumption, going from the steady 1.7GB to 3.6GB and shrinking back to 1.7GB once the request is completed and the response is parsed.

How to reproduce

Perform a clean installation of Hoppscotch Desktop on Windows 11
Start the application while profiling msedgewebview2.exe and hoppscotch.exe processes
Import a collection of around 20 requests
Restart the application and repeat the profile process
Notice the resources consumption differences

Screenshot of the portable desktop app after startup without requests and environments

System configuration

CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz 1.69 GHz
RAM: 16,0 GB
OS: Windows 11 Pro 23H2

Experimental features are completely disabled

Deployment Type

Hoppscotch Cloud

Version

26.1.1

Originally created by @francescodedomenico on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5883 Originally assigned to: @CuriousCorrelation on GitHub. ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Desktop App ### Browser Other (specify in additional info) ### Operating System Windows ### Bug Description ## What happened? Hoppscotch Desktop app on Windows 11 has an huge resources consumption compared to the portable version. <img width="713" height="307" alt="Screenshot of the desktop app during bootstrap" src="https://github.com/user-attachments/assets/d2cbd547-06b8-4912-ac11-af3b4ba62d12" /> > Screenshot of the desktop app during bootstrap The application won't start unless there is enough free RAM available, WebView2 runtime inflates up to 6GB during startup process. If not enough RAM is available the application hangs showing the spinnig wheel rotating in the main window. The issue seems to be related to the handling of the Requests Collection , opening a portable version of Hoppscotch without any environment or requests opens almost instantly and has WebView2 runtime memory footprint of around 400MB, after reimporting my collections and restarting the portable version the Installed Desktop version behavior and memory consumption replicates. Launching an HTTP GET request with a 3.43 json payload causes the consumed memory to have a 2x consumption, going from the steady 1.7GB to 3.6GB and shrinking back to 1.7GB once the request is completed and the response is parsed. ## How to reproduce 1. Perform a clean installation of Hoppscotch Desktop on Windows 11 2. Start the application while profiling msedgewebview2.exe and hoppscotch.exe processes 3. Import a collection of around 20 requests 4. Restart the application and repeat the profile process 5. Notice the resources consumption differences <img width="736" height="336" alt="Image" src="https://github.com/user-attachments/assets/d9852327-c245-4caf-845a-34d4426d3bcf" /> > Screenshot of the portable desktop app after startup without requests and environments ## System configuration CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz 1.69 GHz RAM: 16,0 GB OS: Windows 11 Pro 23H2 Experimental features are completely disabled ### Deployment Type Hoppscotch Cloud ### Version 26.1.1

kerem added the

bug

need testing

labels

2026-03-16 23:56:00 +03:00

kerem commented

2026-03-16 23:56:11 +03:00

Author

Owner

@bart-acc commented on GitHub (Mar 16, 2026):

I can confirm this issue, updated the app to the newest version and problems began. Checked how much memory it consumes with 'performance monitor' and it peaks OVER 16 GIGABYTE!!! on startup on my 32Gig machine. So I've switched over to the portable version and it started in .1 sec without memory spikes.

@bart-acc commented on GitHub (Mar 16, 2026): I can confirm this issue, updated the app to the newest version and problems began. Checked how much memory it consumes with 'performance monitor' and it peaks OVER 16 GIGABYTE!!! on startup on my 32Gig machine. So I've switched over to the portable version and it started in .1 sec without memory spikes.

kerem referenced this issue

2026-03-17 01:19:02 +03:00

[PR #2315] [CLOSED] chore(deps-dev): bump @nuxtjs/eslint-config-typescript from 9.0.0 to 10.0.0 #3730