postmanlabs / postman-app-support

Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIsβ€”faster.
https://www.postman.com
5.84k stars 839 forks source link

Postman eats a lot of CPU and kills it within minutes #11976

Closed jayesh15111988 closed 1 year ago

jayesh15111988 commented 1 year ago

Is there an existing issue for this?

Describe the Issue

Every time I open the Postman app on Mac, my Mac starts making sound as it doing an intensive computation. I am using the latest Postman. My preference has always been using the web client, but it forces me to use the desktop client for uploading file (Which should not be required).

For now, I am trying not to use it as much as possible, but I wonder what makes this seemingly small app CPU hungry within minutes.

Steps To Reproduce

  1. Just open Postman Mac client app

Screenshots or Videos

No response

Operating System

MacOS

Postman Version

10.13.5

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

Nothing else to add

savedario commented 1 year ago

I am having a similar issue. After starting the Postman (v10.14.3 but the previous version was doing the same since a recent update ~12/05/2023), I see 3 'postman' processes using CPU. 2 slowly disappear but one remains using > 130% CPU even though it's doing nothing but drawing the UI. A minute later the fan start spinning (that's how I discovered it). When started from CLI, I see this at the start of the output: The disableGPU setting is set to undefined Not disabling GPU [19472:0518/180624.077216:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process. but the rest is only 'info'. I deleted my install and downloaded and re-installed. The issue remains.

(Running OpenSUSE Tumbleweed 20230517, KDE Plasma 5.27.5, 32GB RAM

jviotti commented 1 year ago

@savedario What is the name of the third process using > 130% CPU? Can you post a screenshot?

sandystorm1990 commented 1 year ago
image
zengzexiong commented 1 year ago

image image The operating system is a windows environment, postman is started, and no requests are run. CPU usage is very high. Updated to latest version, but no change. The current version is v10.17.4

jayesh15111988 commented 1 year ago

Looks like no one really knows what's going on. I guess this is a feature, not a bug! Great job! Closing after 4 months of creating issue with no resolution in mind.

kamalaknn commented 1 year ago

We've fixed this in 10.18. This is being rolled out now. Do update your apps and try it let. Let us know if you are still facing the issue.

snowman commented 11 months ago

image 33331

piotreeeek commented 11 months ago

I'm just installed it, open and immediately fans spinning. Great app, great success, great devs.

panamantis commented 11 months ago

Fresh install Dec 2023, windows 64. Ultra high cpu while idle in background. Used for 15 minutes. If it's been happening for multiple years then likely mining coins.

beryozavv commented 10 months ago

Fresh install Dec 2023, windows 64. Ultra high cpu while idle in background. Used for 15 minutes. If it's been happening for multiple years then likely mining coins.

Same Here. The Postman processes consume about 30% of cpu when the Postman in idle after several requests

attikov commented 8 months ago

It's burning my cpu, killing my notebook, consumes energy, Greta is already out of her mind, please hire an expert.

JorgeSivil commented 8 months ago

It's been happening since I've been using Postman (except early versions).

I don't understand how it can get my processors to 140% without Postman being used. It's just there, open, then your computer starts being very slow, then you notice it's postman.

I'm in Ubuntu.

Is it possible to be related to low memory? I closed all the apps and opened Postman, and no more CPU issues. I had 1.5gb free

danekszy commented 8 months ago

Hey @JorgeSivil, mind sharing any more info about your setup? Which Postman version are you using? Are you working with any large data-sets (lots of requests, big request response etc)? Regarding your question about memory usage: Do you mind checking how much memory is Postman using at the time that you're experiencing the issue? This would be hugely helpful for us to triage what might be happening here! πŸ˜‰ Thanks for pinging us with this! πŸ™Œ

attikov commented 8 months ago

Last time I encountered this issue, I didn't exit Postman; instead, I terminated one of the Postman processes that was using over 600MB of memory and consistently consuming about 14% of CPU resources (equivalent to one core's usage). Killing this process had no impact on Postman's functionality at all. This was on Windows 10 while I was testing the DHL Rest API, which is pretty basic and involves very little data, including base64 encoded labels.

danekszy commented 8 months ago

@attikov Sounds like it could be Service Worker responsible for data synchronization... Are you logged in? Can you check if the changes saved in the app appear on the web version of Postman?

attikov commented 8 months ago

Currently, it is working. I'll check it again next time. By the way, I was not aware that entering sensitive data into Postman could result in it being synced to an unspecified server. I'm not comfortable with this.

kamalaknn commented 8 months ago

@JorgeSivil I want to rule out an issue we had seen earlier.

Could you follow the steps and let us know if you find anything?

  1. Go to View -> Developer -> View logs in Finder
  2. Go to the parent folder
  3. Go to storage folder
  4. Look for any files ending with .lock
JorgeSivil commented 8 months ago

@kamalaknn no lock files

jorgee@jorgee:~/snap/postman/233/.config/Postman/logs$ ls -la
total 19092
drwxrwxr-x  2 jorgee jorgee    4096 ene 17 16:10 .
drwx------ 13 jorgee jorgee    4096 feb 26 12:55 ..
-rw-rw-r--  1 jorgee jorgee   71992 feb 26 12:55 main.log
-rw-rw-r--  1 jorgee jorgee     305 abr  3  2023 renderer-auth.log
-rw-rw-r--  1 jorgee jorgee 5244083 oct 13 13:30 renderer-requester1.log
-rw-rw-r--  1 jorgee jorgee 5245149 ene 11 15:29 renderer-requester2.log
-rw-rw-r--  1 jorgee jorgee 3349744 feb 26 13:52 renderer-requester3.log
-rw-rw-r--  1 jorgee jorgee  176409 ene 17 10:29 renderer-requester4.log
-rw-rw-r--  1 jorgee jorgee 5246257 sep  6 12:50 renderer-requester.log
-rw-rw-r--  1 jorgee jorgee  170419 feb 26 12:55 renderer-shell.log

bwt I have less than 50 requests

main.log renderer-requester3.log renderer-shell.log

What info do you need next time it happens

kamalaknn commented 8 months ago

@JorgeSivil Thanks for getting back with the logs.

The lock files if present should be in ~/snap/postman/233/.config/Postman/storage. The details you have shared are for the logs directory. Could you check the storage directory?

Also it seems that you are on version 9.31.30. We fixed one of the high CPU issues in a v10 version. Could you update your app to the latest version and let us know if this is still an issue?

JorgeSivil commented 8 months ago

@JorgeSivil Thanks for getting back with the logs.

The lock files if present should be in ~/snap/postman/233/.config/Postman/storage. The details you have shared are for the logs directory. Could you check the storage directory?

Also it seems that you are on version 9.31.30. We fixed one of the high CPU issues in a v10 version. Could you update your app to the latest version and let us know if this is still an issue?

jorgee@jorgee:~$ ls -la  ~/snap/postman/233/.config/Postman/storage
total 20
drwxrwxr-x  2 jorgee jorgee 4096 feb 26 12:55 .
drwx------ 13 jorgee jorgee 4096 feb 26 12:55 ..
-rw-rw-r--  1 jorgee jorgee   39 feb 26 12:55 requester.json
-rw-rw-r--  1 jorgee jorgee   58 feb 26 12:55 settings.json
-rw-rw-r--  1 jorgee jorgee  546 feb 26 12:55 userPartitionData.json
simeyla commented 8 months ago

I'm on Windows and haven't done much investigation, but my fans were out of control for hours and it was using 30% CPU with nothing happening - even when minimized.

On closing and reopening I got a message about Windows Firewall having blocked Postman. I rarely use it - let alone have it open for an entire day, so I don't know if this is a new issue or not for me. I didn't check for a .lock file while it was slow.

If it is as simple as not having network access and it keeps retying then that seems like a trivial fix that shouldn't have ever been an issue in the first place. I'll edit this if the problem returns.

shreyakqss commented 8 months ago

I just ended up using the web version of Postman with desktop agent. Having 30% CPU usage in idle on Windows x64

kamalaknn commented 8 months ago

@shreyakqss Could you help us with some additional information to identify the cause for the issues?

  1. Could you share the application logs with us at help@postman.com? If you are able to open the app you can find them under View -> Developer -> View logs in Explorer.
  2. Could you share the list of files present in the storage directory, it should be in C:\Users\<user>\AppData\Local\Postman\storage or C:\Users\<user>\AppData\Roaming\Postman\storage.
wileyveteran commented 7 months ago

My postman app (on Windows) was using 25-30% of CPU so I checked the C:\Users\\AppData\Roaming\Postman\storage folder and had a settings.json.lock file and another for userPartitionData.json that was suffixed with STALE. I shutdown Postman to make sure nothing was running, deleted both of those files and restarted postman and Postman CPU is now back to 0 when not using it.

marius-oloeru commented 7 months ago

In my case disabling hardware acceleration fixed the problem.

ZakariaX1 commented 5 months ago

In my case disabling hardware acceleration fixed the problem.

This seems to be the best solution so far, I would love to know what this hardware acceleration is doing for the app πŸ€” I don't notice any difference in the rendering of the app/visuals, so I'd love to know what it's doing. Thanks @marius-oloeru !

armandomejiam commented 5 months ago

TL;DR disabling hardware acceleration works for me!

I uninstalled Postman months ago because of this issue, the laptop fan was always noisy when the Postman app was open, and then when I checked the resources on the Task Manager, the CPU consumption was always too high.

The thing is I need Postman, and the VS Code extension was not suitable for me, nor the web client...

So I installed the app again today and the CPU went high usage again in matter of minutes, so I disabled the hardware acceleration and this time it seems to be behaving decently.

Thanks @marius-oloeru

snowman commented 5 months ago

To disable Hardware acceleration, read Troubleshoot app issues - Postman Learning Center

Hardware acceleration

Postman takes advantage of your computer's built-in graphics hardware to speed up the rendering of onscreen graphics.

Sometimes your computer's specific GPU, drivers, or operating system may cause issues with hardware acceleration.

If you see screen artifacts or other glitches, turning off hardware acceleration might solve the problem.

To activate or deactivate hardware acceleration in Postman:

On macOS,            select Postman > Hardware Acceleration
On Windows or Linux, select Help    > Hardware Acceleration

Restart Postman to apply the new setting. Disabling hardware acceleration may affect performance or CPU usage.

Vignatus commented 5 months ago

@marius-oloeru Thanks Disabling hardware acceleration for version 11.1.25 reduced the memory footprint from above 2 GB to ~260 MB on Mac M1. More like Hardware Deceleration.

Unless this issue is fixed, future updates should keep it off as default

madzohan commented 3 months ago

lol i thought it has integrated crypto miner πŸ˜„ it's not fixed YET 😞 on 11.5.1-ui-240724-0915

lantanios commented 2 weeks ago

lol i thought it has integrated crypto miner πŸ˜„ it's not fixed YET 😞 on 11.5.1-ui-240724-0915

Having this issue on Version 11.17.1

Has anyone inspected traffic with Wireshark or analyzed what is actually going on?

It can be a backdoor into computer.

Why it's so hard to resolve?

numaanashraf commented 2 weeks ago

@lantanios Could you try disabling 'hardware acceleration'?