starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #3563] [bug]: Desktop app eats 67% of my CPU rendering the flashing indicator thing showing the selected request #1221

New issue

Open

opened 2026-03-16 19:22:05 +03:00 by kerem · 9 comments

kerem commented

2026-03-16 19:22:05 +03:00

Owner

Originally created by @rstat1 on GitHub (Nov 18, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3563

Originally assigned to: @CuriousCorrelation on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Current behavior

Running the desktop app with a single request in the list. Having it selected renders a flashing green indicator next to it. As long as said indicator is visible, 3 processes on my machine (XWayland, gnome-shell, and hoppscotch's webkit renderer process) consume a combined amount of the CPU that I've seen reach as high as 67%. Once I collapse the sidebar or navigate to a page in the app where the request list is not visible this behavior stops.

I feel like this might be a bit excessive. I see similarly (but not as bad) excessive CPU use in Firefox, and deleting the elements driving that flashing indicator in Firefox's devtools box, seem to lower the CPU use back to what I'd consider acceptable.

Steps to reproduce

Using Fedora 39 in its default configuration on a machine with an Intel integrated GPU
Download the Hoppscotch AppImage
Add a single request and make sure it's selected.
Open a terminal
Type top -d2
Observe high CPU usage in the above named processes
Return the Hoppscotch app and collapse the sidebar or navigate to the settings page
Return the terminal app
Observe the now lowered CPU usage.

Environment

Production

Version

Local

Originally created by @rstat1 on GitHub (Nov 18, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3563 Originally assigned to: @CuriousCorrelation on GitHub. ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior Running the desktop app with a single request in the list. Having it selected renders a flashing green indicator next to it. As long as said indicator is visible, 3 processes on my machine (XWayland, gnome-shell, and hoppscotch's webkit renderer process) consume a combined amount of the CPU that I've seen reach as high as 67%. Once I collapse the sidebar or navigate to a page in the app where the request list is not visible this behavior stops. I feel like this might be a bit excessive. I see similarly (but not as bad) excessive CPU use in Firefox, and deleting the elements driving that flashing indicator in Firefox's devtools box, seem to lower the CPU use back to what I'd consider acceptable. ### Steps to reproduce 1. Using Fedora 39 in its default configuration on a machine with an Intel integrated GPU 2. Download the Hoppscotch AppImage 3. Add a single request and make sure it's selected. 4. Open a terminal 5. Type top -d2 6. Observe high CPU usage in the above named processes 7. Return the Hoppscotch app and collapse the sidebar or navigate to the settings page 8. Return the terminal app 9. Observe the now lowered CPU usage. ### Environment Production ### Version Local

kerem added the

bug

need testing

desktop

labels

2026-03-16 19:22:05 +03:00

kerem commented

2026-03-16 19:22:16 +03:00

Author

Owner

@AyoItsYas commented on GitHub (Jan 22, 2025):

A feature to run hoppscotch with reduced motion or animations would be really nice. I don't know if there are any electron flags that can easily be leveraged to mitigate the issue.

@AyoItsYas commented on GitHub (Jan 22, 2025): A feature to run hoppscotch with reduced motion or animations would be really nice. I don't know if there are any electron flags that can easily be leveraged to mitigate the issue.

kerem commented

2026-03-16 19:22:21 +03:00

Author

Owner

@Rudde commented on GitHub (Feb 3, 2025):

I'm also struggling to run hoppscotch on an old laptop it has an i7-5600U and hoppscotch easily pushed it to 100% load if it is currently at 40% load when launching. Even when I don't do anything or have it in focus it still eat up the CPU. Postman does not seem to cause this behavior, I assume they also run on electron?

My laptop is running Linux Mint.

@Rudde commented on GitHub (Feb 3, 2025): I'm also struggling to run hoppscotch on an old laptop it has an i7-5600U and hoppscotch easily pushed it to 100% load if it is currently at 40% load when launching. Even when I don't do anything or have it in focus it still eat up the CPU. Postman does not seem to cause this behavior, I assume they also run on electron? My laptop is running Linux Mint.

kerem commented

2026-03-16 19:22:26 +03:00

Author

Owner

@jacksitlab commented on GitHub (Feb 20, 2025):

same on my side. working with XUbuntu 24.04 and X11, but it makes no difference if I am on REST page or on Settings page or if sidebar is collapsed or not. CPU is always at around 70% (in top around 430%) usage for ././/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 12 16

I also tested it with arch+gnome+wayland and it is not behaving like this. so maybe wayland vs x11?

@jacksitlab commented on GitHub (Feb 20, 2025): same on my side. working with XUbuntu 24.04 and X11, but it makes no difference if I am on REST page or on Settings page or if sidebar is collapsed or not. CPU is always at around 70% (in top around 430%) usage for `././/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 12 16` I also tested it with arch+gnome+wayland and it is not behaving like this. so maybe wayland vs x11?

kerem commented

2026-03-16 19:22:31 +03:00

Author

Owner

@rstat1 commented on GitHub (Feb 20, 2025):

same on my side. working with XUbuntu 24.04 and X11, but it makes no difference if I am on REST page or on Settings page or if sidebar is collapsed or not. CPU is always at around 70% (in top around 430%) usage for ././/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 12 16

I also tested it with arch+gnome+wayland and it is not behaving like this. so maybe wayland vs x11?

Nah it's a problem on Wayland too. That's what I was using when I wrote this report.

@rstat1 commented on GitHub (Feb 20, 2025): > same on my side. working with XUbuntu 24.04 and X11, but it makes no difference if I am on REST page or on Settings page or if sidebar is collapsed or not. CPU is always at around 70% (in top around 430%) usage for `././/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 12 16` > > I also tested it with arch+gnome+wayland and it is not behaving like this. so maybe wayland vs x11? Nah it's a problem on Wayland too. That's what I was using when I wrote this report.

kerem commented

2026-03-16 19:22:36 +03:00

Author

Owner

@Rudde commented on GitHub (Feb 20, 2025):

I don't know if this is helpful but if you make the hoppscotch window really small but keep it running, the load will disappear.

@Rudde commented on GitHub (Feb 20, 2025): I don't know if this is helpful but if you make the hoppscotch window really small but keep it running, the load will disappear.

kerem commented

2026-03-16 19:22:41 +03:00

Author

Owner

@liyasthomas commented on GitHub (Mar 4, 2025):

Thanks for your patience and valuable feedback. We’ve fixed this bug in the latest release.
Download the latest builds and provide your valuable feedback.

Closing this ticket as this bug is now fixed in the recent version. Please feel free to reach out if you have any other concerns.

@liyasthomas commented on GitHub (Mar 4, 2025): Thanks for your patience and valuable feedback. We’ve fixed this bug in the latest release. [Download the latest builds](https://hoppscotch.com/download) and provide your valuable feedback. Closing this ticket as this bug is now fixed in the recent version. Please feel free to reach out if you have any other concerns.

kerem commented

2026-03-16 19:22:46 +03:00

Author

Owner

@Rudde commented on GitHub (Mar 11, 2025):

This does not seem to have solved the issue for me.

@Rudde commented on GitHub (Mar 11, 2025): This does not seem to have solved the issue for me.

kerem commented

2026-03-16 19:22:51 +03:00

Author

Owner

@jacksitlab commented on GitHub (Mar 12, 2025):

neither for me

Hoppscotch v2025.2.1

@jacksitlab commented on GitHub (Mar 12, 2025): neither for me ``` Hoppscotch v2025.2.1 ```

kerem commented

2026-03-16 19:22:57 +03:00

Author

Owner

@rstat1 commented on GitHub (Nov 2, 2025):

Ok so after 2 yrs I think we finally call this mostly fixed. Not sure why (or how) it took 2yrs to remove a flashing circle, but I am glad you finally did in your most recent 2025.10.0 release.

There still seems to be an issue with the little animated highlight around the notification box that appeared in the bottom left of the window, causing the same CPU usage problem but closing it stops the problem.

@rstat1 commented on GitHub (Nov 2, 2025): Ok so after 2 yrs I think we finally call this mostly fixed. Not sure why (or how) it took 2yrs to remove a flashing circle, but I am glad you finally did in your most recent 2025.10.0 release. There still seems to be an issue with the little animated highlight around the notification box that appeared in the bottom left of the window, causing the same CPU usage problem but closing it stops the problem.

kerem referenced this issue

2026-03-17 00:47:22 +03:00

[PR #1221] [MERGED] Fix: ios home bar covers content #3146

kerem referenced this issue

2026-03-17 00:47:54 +03:00

[PR #1230] [MERGED] Upstream #3156