'Why is Postman crashing right after startup

Postman is crashing about 5 seconds after starting. My last operation was a bulk load for ElasticSearch. The load worked as far as I can tell. Now Postman crashes. I have tried restarting several times, but all it does is hang for a few seconds and then crash.

I have Chrome version 56. Postman version: 4.10.4



Solution 1:[1]

In case someone else is also facing this problem, Postman stores all its data locally in an application-specific indexed DB file. In my case also, the data got bit too large and postman started crashing.Following steps might help, they did in my case:

  1. chrome://indexeddb-internals

  2. Look for: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop

  3. Under the "Paths:" section note the location of the chrome-extension_fhbjgbiflinjbdggehcddcbncdddomop_0.indexeddb.leveldb folder

  4. Navigate to this location on your local system.

  5. Copy this entire contents of this folder and save it to a safe location on your local system to be used later (your collections will be in DB file in this folder)

  6. Remove the Postman extension from Chrome and then Re-Add the postman extension.

Postman should open but it will be default settings with none of your collections.

Solution 2:[2]

If you're in Linux just execute the following command from the terminal and start postman again

pkill -fi Postman

Solution 3:[3]

Go To:

C:\Users\%Username%\AppData\Local\Google\Chrome\User Data\Default\Storage\ext\fhbjgbiflinjbdggehcddcbncdddomop\def\IndexedDB\chrome-extension_fhbjgbiflinjbdggehcddcbncdddomop_0.indexeddb.leveldb\

Rename *.log files

And relaunch postman

Solution 4:[4]

I have deleted all files from the below folder and launched Postman. Crashing issue is solved. (To be on the safe side, I took a backup of this folder before deleting.)

C:\Users\%User%\AppData\Local\Google\Chrome\User Data\Default\Storage\ext\fhbjgbiflinjbdggehcddcbncdddomop\def\IndexedDB\chrome-extension_fhbjgbiflinjbdggehcddcbncdddomop_0.indexeddb.leveldb

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Kirk Beard
Solution 2 bahdotsh
Solution 3 Ahmad Raeiji
Solution 4 Jeremy Caney