Slow application consuming a lot my memory and system CPU

[jperucello]

Postman application gets really slow and uses too much of my memory/CPU

To Reproduce Steps to reproduce the behavior:

1. Open the Postman app (windows or Mac)
2. Use your collections and send the requests Result: After a few minutes using the app, it becomes really slow, the calls takes a long time to be opened as a tab

Expected behavior When I click on a request, I need it to open and be ready to be send

Screenshots

App information (please complete the following information):

• Native App
• Postman Version v7.6.0
• OS: Windows 10 and macOS Mojave v10.14.6

Additional context It's been a while since is like that (since I started using it really), but since last updates is even worse, I have to force stop the application and clean the cache at least 5 times a day to be able to use the application in a acceptable speed.

[Mr3dfx]

While continuing to have this issue, I discovered a super double top secret build that has helped me across the board, display rendering and performance issues. It's called 'Canary' build,

https://www.postman.com/downloads/canary

WARNING This is kind of a 'feature' branch, so using it may have unintended issues, HOWEVER, it can be run side-by-side the released build (which I can confirm).

Of, course read all the disclaimers and warnings before using, but I could not stand the performance in the release build, it was actually becoming a hindrance to use so I took the plunge and took the canary into my coal mine with decent results.

[numaanashraf]

@Mr3dfx Great to hear that performance has improved for you with our Canary build. Canary is our early access release channel, and the same improvements will roll out to stable this week. :)

[TehBakker]

I can't use Postman anymore, it goes up over 100% CPU as soon as I start it and the fan goes in crazy mode. Any update on this? Else I'll have to find another soft quick, because I've most of my dev test requestes there and it's hell without it atm.

[kamalaknn]

Hey @TehBakker

Are you signed into Postman? Can you try signing out and signing back in?

[ayavvv]

v7.22.1 still doesn't work.

So I downgrade to v7.11.0 it works fine!

[jtktam]

To consistently reproduce the same behavior using the runner

1. do a few large runs (50,000 post request, 700 bytes per request, 5-6 runs) during each run the history never updates with the current run, runner stays black screen
2. quit out of the runner window
3. restart runner, history is shown
4. delete all on history, spinning icon comes up, nothing works now.. only can quit the runner window

now look at process manager / task manager.. one task will take up a lot of cpu cycles

nothing you can do (killing it, restart, etc) will fix this.. i had to basically delete some cache, etc and hope it doesn't ruin my colllections

[jtktam]

EXPORT YOUR COLLECTIONS FIRST

i just confirmed that if you are stuck with the postman starting or loading runner, if you clear out the leveldb directory it works fine again BUT you will lose all your collections.. luckily i had exported it beforehand

[TehBakker]

Hey @TehBakker

Are you signed into Postman? Can you try signing out and signing back in?

Hey, i logged out and in but also cleaned the whole history, which took forever. And it's better now, thanks.

[jlevitt]

v7.23.0 seems much improved. Still using 500MB RAM, but the interface feels snappy. It hasn't felt like this in over a year.

[jlivet]

I've had repeated problems with performance in Postman for the past couple of months when trying to change an environment variable. I have about 50 variables and 75 environments. It is at the point where it is locking up completely the minute I try to change a variable. I just tried clearing my History but that didn't help. I was on v7.23.0.

I love the app but it is unusable at this point because I need to update some of the environments and if I try to backspace over 1 character in a variable value, it locks up.

I took the advice above and downgraded to what I thought was 7.11 but is actually 7.1.1 and I'm able to change environments. Not sure what the problem is but the newer version of Postman seems to be taking up lots of memory and the environment section is slow.

[leibson]

subramanya.raj - Per your request, I am adding my experience to this thread. https://community.postman.com/t/postman-7-24-0-cpu-83-memory-very-high/12575?u=guylev

This is for 7.24.0.
I am using a free (eval) version. Maybe that has to do with it. I know there's a request limit.

I checked this: https://github.com/postmanlabs/postman-app-support/issues/7370 and this: https://github.com/postmanlabs/postman-app-support/issues/7294.

I start Postman and almost immediately it freezes before I can even do anything like delete history or open a collection. I don't save history anyway, so that should not be an issue.

I have less than 20 collection and only 3 environments.

I closed and opened Postman, and I restarted the laptop.

Now when I run PM, the screen is totally black. I can get to my collections by opening a new Postman window.

The button spins very often.

It is impossible for me to use PM at this point.

[leibson]

subramanya.raj - Per your request, I am adding my experience to this thread. https://community.postman.com/t/postman-7-24-0-cpu-83-memory-very-high/12575?u=guylev

This is for 7.24.0. I am using a free (eval) version. Maybe that has to do with it. I know there's a request limit.

I checked this: #7370 and this: #7294.

I start Postman and almost immediately it freezes before I can even do anything like delete history or open a collection. I don't save history anyway, so that should not be an issue.

I have less than 20 collection and only 3 environments.

I closed and opened Postman, and I restarted the laptop.

Now when I run PM, the screen is totally black. I can get to my collections by opening a new Postman window.

The button spins very often.

It is impossible for me to use PM at this point.

I think I found the problem. I was on a team (which I did not need to be on).
I had exceeded the shared history limit. I removed myself from the team and, since I'm now on no teams, the shared value for everything is down to 0. So far, so good.

[Tallon159]

Postman seems to be spending most of its time beating the hell out of the AppData/Roaming/Postman/storage folder or a file within it. It took me a couple of seconds to collect over half a million events in ProcMon, that just seem to be an endless repetition of what you see in the screenshot below:

It was doing this even after I closed the app and the main window wasn't visible. One process remained active, taking 60% CPU and accessing this path hundreds of thousands of times a second. Without postman running, and my system relatively idle (one browser tab, task manager, few background apps), there are ~ 32 000 events per second. With Postman running this rises to ~65 000 events per second

This is the right answer for the problem i was facing on v7.25.0. I attach my folder storage for debugging purpose. storage_old.zip

[maxdeepfield]

[igor-d-n]

Same shit( Ubuntu 18.04 Postman 7.25.0 Remaining after I closed app. What is it? Some added mining backdoor?)

[jimmy0699]

Postman Version 7.25.2 MacOS Catalina 10.15.4 (19E287)

[nagahshi]

Deepin 15.11

Postman v7.27.1 - renderer problem guys

[JamesElliott-Wren]

Got the same memory issues. left with a blank screen after a few seconds of opening a new window.

[ndrd]

@arlemi #8751 and #7294 are closed and they are circular referenced, there is a real solution to this issue?

[ranjith19]

I face this every day. My current job involves dealing with a lot of APIs and postman is a really bad experience to work with. It is too slow. In my team we have about 50 collections.

Postman needs to improve or we will need to move to some other tool :-(

[Raj-postman]

Hi @ranjith19 - Sorry to hear about the experience. Could you please write to us at help@postman.com with the application version and the details around the issue? We will check on this further.

[ndrd]

@ranjith19 try updating to canary, it has better performance

[kwbhatti]

I had the same issue guys. Here is how I resolved it.

1. make sure that if you are saving your web traffic using proxy or interceptor, do turn that off or look at where the calls a being saved. This would take too much memory saved to History or any other collection that you are saving the requests to.
2. clear history is you do not plan on using anything there. I had so much in history that the app froze trying to delete the history.
3. make sure all the un-used tabs are closed. I tend to keep them open and never save them, and I believe that this is very common for most of the users.

Hope this helps, for a couple of weeks I kept thinking that something is wrong with postman but it is working fine for me now.

[ranjith19]

@ndrd I just installed. Hope this canary version is faster

[SquirrelCoder]

Sadly I had to uninstall Postman! Postman simply takes all my RAM, all my resource and you guys won't even consider so many comments on this issue, simply every single person has a problem with it! The canary was also no help, it stucks simply on formatting the response and I have to force close the app.

[arlemi]

@SquirrelCoder You may be interested in giving Postman for the Web a try: https://go.postman.co/build

Learn more about it in our blog post (TL;DR, it's the Postman experience in your browser): https://blog.postman.com/announcing-postman-for-the-web-now-in-open-beta/

[EwertonDutra]

same problem

Consuming a lot of CPU (30% and never stops) version 7.30.1 Windows 10 64 bits

[josh-endries]

Just happened to me (that I noticed). When I closed it, the UI went away, but it kept using 50-90% CPU for maybe 30 seconds before it went away in Task Manager.

[EwertonDutra]

PostmanCanary for now it's working for me!

[JamesElliott-Wren]

I have this issue using My Mac computer at work, but if I use a windows laptop, it works fine.

[jwong-konrad]

@SquirrelCoder You may be interested in giving Postman for the Web a try: https://go.postman.co/build

Learn more about it in our blog post (TL;DR, it's the Postman experience in your browser): https://blog.postman.com/announcing-postman-for-the-web-now-in-open-beta/

This actually helps TREMENDOUSLY, thank you for the suggestion. Even Postman Canary is still a resource hog, I don't know how Chrome is reigning in Postman's resource consumption but I'll take the win.

[atom88888]

@jlevitt We are looking into the cause for these issues. Could you give us a bit more information to help us identify the root cause?

1. How many request tabs do you have open?
2. How many saved requests/collections do you have?
3. What is the average size of the request in the tab/collection/history?
4. How many variables do you have in your active environment?

I have noticed the same thing when I only have 2-3 tabs open but a local "collection" of 150-300 requests. I think perhaps a large number of collections is causing CPU / memory issues. I have had to prune down my number of stored / saved requests in order to improve postman's performance. At first I thought it was my computer or OS but when I closed POSTMAN my system resumed normal response times.

[atom88888]

I had the same issue guys. Here is how I resolved it.

1. make sure that if you are saving your web traffic using proxy or interceptor, do turn that off or look at where the calls a being saved. This would take too much memory saved to History or any other collection that you are saving the requests to.
2. clear history is you do not plan on using anything there. I had so much in history that the app froze trying to delete the history.
3. make sure all the un-used tabs are closed. I tend to keep them open and never save them, and I believe that this is very common for most of the users.

Hope this helps, for a couple of weeks I kept thinking that something is wrong with postman but it is working fine for me now.

that's a great idea, where do you find those settings? How to you clear it out if you find them?

[cretara]

Hi all, i have issue in my Windows 10 x64 pc at work

I cannot sync my API with other pc i use

[abernoth]

Thanks for the pointers - I stopped the Postman Agent - looks like it logs everything passing through. If there was a feature to control what it logged or how much I guess I'd leave it running. Stopping it stopped the excessive API call logs and returned Postman App to a much better response time.

[cretara]

Hi all, i have issue in my Windows 10 x64 pc at work

I cannot sync my API with other pc i use

Hi all, solved this issue by download, installing and using Postman Canary. Same issue for a colleague using Mac client.

I couldn't solve by stopping Postman agent.

[Ragnoroct]

WORKAROUND: Deleting my C:\Users\<username>\AppData\Roaming\Postman\storage folder or renaming it after closing Postman and force closing zombie processes in task manager fixed the issue. (for now)

10:54:25.8008096 AM Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
10:54:25.8008552 AM Postman.exe 7916    QueryAllInformationFile C:\Users\<username>\AppData\Roaming\Postman\storage BUFFER OVERFLOW CreationTime: 1/11/2019 9:21:29 AM, LastAccessTime: 11/6/2020 10:54:25 AM, LastWriteTime: 11/6/2020 9:57:43 AM, ChangeTime: 11/6/2020 9:57:43 AM, FileAttributes: D, AllocationSize: 4,096, EndOfFile: 4,096, NumberOfLinks: 1, DeletePending: False, Directory: True, IndexNumber: 0x7000000004a74, EaSize: 0, Access: Read Attributes, Synchronize, Position: 0, Mode: Synchronous IO Non-Alert, AlignmentRequirement: Word
10:54:25.8008702 AM Postman.exe 7916    QueryInformationVolume  C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS VolumeCreationTime: 12/19/2017 12:45:26 PM, VolumeSerialNumber: C689-F6F3, SupportsObjects: True, VolumeLabel: 
10:54:25.8008830 AM Postman.exe 7916    CloseFile   C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS 
10:54:25.8009208 AM Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage NAME COLLISION  Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
10:54:25.8009727 AM Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage NAME COLLISION  Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
10:54:25.8010309 AM Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage\requester.json.lock NAME COLLISION  Desired Access: Generic Write, Read Attributes, Disposition: Create, Options: Synchronous IO Non-Alert, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: 0
10:54:25.8011036 AM Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage NAME COLLISION  Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
10:54:25.8011695 AM Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
10:54:25.8012286 AM Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage\requester.json.lock NAME COLLISION  Desired Access: Generic Write, Read Attributes, Disposition: Create, Options: Synchronous IO Non-Alert, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: 0
10:54:25.8012385 AM Postman.exe 7916    QueryAllInformationFile C:\Users\<username>\AppData\Roaming\Postman\storage BUFFER OVERFLOW CreationTime: 1/11/2019 9:21:29 AM, LastAccessTime: 11/6/2020 10:54:25 AM, LastWriteTime: 11/6/2020 9:57:43 AM, ChangeTime: 11/6/2020 9:57:43 AM, FileAttributes: D, AllocationSize: 4,096, EndOfFile: 4,096, NumberOfLinks: 1, DeletePending: False, Directory: True, IndexNumber: 0x7000000004a74, EaSize: 0, Access: Read Attributes, Synchronize, Position: 0, Mode: Synchronous IO Non-Alert, AlignmentRequirement: Word
10:54:25.8012671 AM Postman.exe 7916    QueryInformationVolume  C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS VolumeCreationTime: 12/19/2017 12:45:26 PM, VolumeSerialNumber: C689-F6F3, SupportsObjects: True, VolumeLabel: 
10:54:25.8012854 AM Postman.exe 7916    CloseFile   C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS 
10:54:25.8013115 AM Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
10:54:25.8013614 AM Postman.exe 7916    QueryAllInformationFile C:\Users\<username>\AppData\Roaming\Postman\storage BUFFER OVERFLOW CreationTime: 1/11/2019 9:21:29 AM, LastAccessTime: 11/6/2020 10:54:25 AM, LastWriteTime: 11/6/2020 9:57:43 AM, ChangeTime: 11/6/2020 9:57:43 AM, FileAttributes: D, AllocationSize: 4,096, EndOfFile: 4,096, NumberOfLinks: 1, DeletePending: False, Directory: True, IndexNumber: 0x7000000004a74, EaSize: 0, Access: Read Attributes, Synchronize, Position: 0, Mode: Synchronous IO Non-Alert, AlignmentRequirement: Word

https://docs.microsoft.com/en-us/sysinternals/downloads/procmon This trace of calls was gathered by Microsoft's Process Monitor sysinternals tool. It might be related to the requester.json.lock file.

This is my storage folder I renamed to try to fix the problem (which it did). storage_old.zip

[cretara]

WORKAROUND: Deleting my C:\Users\<username>\AppData\Roaming\Postman\storage folder or renaming it after closing Postman and force closing zombie processes in task manager fixed the issue. (for now)

10:54:25.8008096 AM   Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
10:54:25.8008552 AM   Postman.exe 7916    QueryAllInformationFile C:\Users\<username>\AppData\Roaming\Postman\storage BUFFER OVERFLOW CreationTime: 1/11/2019 9:21:29 AM, LastAccessTime: 11/6/2020 10:54:25 AM, LastWriteTime: 11/6/2020 9:57:43 AM, ChangeTime: 11/6/2020 9:57:43 AM, FileAttributes: D, AllocationSize: 4,096, EndOfFile: 4,096, NumberOfLinks: 1, DeletePending: False, Directory: True, IndexNumber: 0x7000000004a74, EaSize: 0, Access: Read Attributes, Synchronize, Position: 0, Mode: Synchronous IO Non-Alert, AlignmentRequirement: Word
10:54:25.8008702 AM   Postman.exe 7916    QueryInformationVolume  C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS VolumeCreationTime: 12/19/2017 12:45:26 PM, VolumeSerialNumber: C689-F6F3, SupportsObjects: True, VolumeLabel: 
10:54:25.8008830 AM   Postman.exe 7916    CloseFile   C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS 
10:54:25.8009208 AM   Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage NAME COLLISION  Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
10:54:25.8009727 AM   Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage NAME COLLISION  Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
10:54:25.8010309 AM   Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage\requester.json.lock NAME COLLISION  Desired Access: Generic Write, Read Attributes, Disposition: Create, Options: Synchronous IO Non-Alert, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: 0
10:54:25.8011036 AM   Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage NAME COLLISION  Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
10:54:25.8011695 AM   Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
10:54:25.8012286 AM   Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage\requester.json.lock NAME COLLISION  Desired Access: Generic Write, Read Attributes, Disposition: Create, Options: Synchronous IO Non-Alert, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: 0
10:54:25.8012385 AM   Postman.exe 7916    QueryAllInformationFile C:\Users\<username>\AppData\Roaming\Postman\storage BUFFER OVERFLOW CreationTime: 1/11/2019 9:21:29 AM, LastAccessTime: 11/6/2020 10:54:25 AM, LastWriteTime: 11/6/2020 9:57:43 AM, ChangeTime: 11/6/2020 9:57:43 AM, FileAttributes: D, AllocationSize: 4,096, EndOfFile: 4,096, NumberOfLinks: 1, DeletePending: False, Directory: True, IndexNumber: 0x7000000004a74, EaSize: 0, Access: Read Attributes, Synchronize, Position: 0, Mode: Synchronous IO Non-Alert, AlignmentRequirement: Word
10:54:25.8012671 AM   Postman.exe 7916    QueryInformationVolume  C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS VolumeCreationTime: 12/19/2017 12:45:26 PM, VolumeSerialNumber: C689-F6F3, SupportsObjects: True, VolumeLabel: 
10:54:25.8012854 AM   Postman.exe 7916    CloseFile   C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS 
10:54:25.8013115 AM   Postman.exe 7916    CreateFile  C:\Users\<username>\AppData\Roaming\Postman\storage SUCCESS Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
10:54:25.8013614 AM   Postman.exe 7916    QueryAllInformationFile C:\Users\<username>\AppData\Roaming\Postman\storage BUFFER OVERFLOW CreationTime: 1/11/2019 9:21:29 AM, LastAccessTime: 11/6/2020 10:54:25 AM, LastWriteTime: 11/6/2020 9:57:43 AM, ChangeTime: 11/6/2020 9:57:43 AM, FileAttributes: D, AllocationSize: 4,096, EndOfFile: 4,096, NumberOfLinks: 1, DeletePending: False, Directory: True, IndexNumber: 0x7000000004a74, EaSize: 0, Access: Read Attributes, Synchronize, Position: 0, Mode: Synchronous IO Non-Alert, AlignmentRequirement: Word

https://docs.microsoft.com/en-us/sysinternals/downloads/procmon This trace of calls was gathered by Microsoft's Process Monitor sysinternals tool. It might be related to the requester.json.lock file.

This is my storage folder I renamed to try to fix the problem (which it did). storage_old.zip

Hi, following your advice and monitoring processes with procmon, i had to rename my folder

C:\Users\<user>\AppData\Roaming\Postman\IndexedDB

with postman not running to get Postman back. Thank you for useful information

[shelbaz]

Multiple threads open about this: https://github.com/postmanlabs/postman-app-support/issues/4687

[nthdeveloper]

I have updated the app to v8.0.3 but the situation still the same. My CPU fan goes crazy when I run Postman and does not stop until I close it. Tried to delete settings, database, backup... files but nothing changed.

[alexs20]

The same issue on Linux Mint I feel like this app is running crypto mining on background...

[morsapt]

Using 8.0.6 version I got the same high CPU usage on Windows 10. The solution provided by @Ragnoroct worked for me.

[vbond007]

Hi all, I confirm that the workaround suggested by Ragnoroct worked : Deleting my C:\Users\\AppData\Roaming\Postman\storage folder !

[AlexanderChaker]

I noticed that High Usage happens when there is an update that's auto-downloaded, and it's waiting to be installed. Even when I'm not actively working with Postman, and all tabs are closed. Usage stays high until I install and restart. This has been the case for several version older, and still happened today for v8.5.1 notification.

[Rukko]

I noticed that High Usage happens when there is an update that's auto-downloaded, and it's waiting to be installed. Even when I'm not actively working with Postman, and all tabs are closed. Usage stays high until I install and restart. This has been the case for several version older, and still happened today for v8.5.1 notification.

Exactly. This happened to me today, too. My Postman was minimized but it was consuming 90% of CPU until I applied the update and restarted it.

[vbiginner]

Auto downloading is one of the causes. Why there is no option to disable downloading minor updates.. it just eating out all the available data, causing issues when you are working with limited data. Already there was issue raised here https://github.com/postmanlabs/postman-app-support/issues/6757#issue-458242538 and it is closed without any solution

[arlemi]

@vbiginner This is being tracked in https://github.com/postmanlabs/postman-app-support/issues/6999.

[jviotti]

Hey there! As @vbiginner, mentioned, auto-updates on Windows is one of the main causes of high CPU usage..

We've identified that the problem is how the application performs delta updates. Disabling delta updates (something we as a team can do when building the application from source) brings down the CPU usage of the "Update" process to a minimum while the update is downloaded and applied. However, non-delta auto-updates will consume significantly more bandwidth, so we are looking for a solution to perform deltas without sacrificing performance!

[Makesh-Gmak]

I noticed that High Usage happens when there is an update that's auto-downloaded, and it's waiting to be installed. Even when I'm not actively working with Postman, and all tabs are closed. Usage stays high until I install and restart. This has been the case for several version older, and still happened today for v8.5.1 notification.

I observed Postman always consuming 10-15%, even in its idle mode. After I restart, I saw upgrade notification and there after CPU is < 1%. So, till you apply the upgrade, you need to sacrifice your CPU cycles for Postman. This needs to be fixed. OS: Win 10

[jviotti]

@Makesh-Gmak

So, till you apply the upgrade, you need to sacrifice your CPU cycles for Postman.

That's interesting information. Thanks for sharing this. We are in the process of evaluating the auto-update technology we use for Windows and see if we can make progress and all these issues in one batch. Stay tuned!