Postman after update to 6.3.1 freeze loading

[siryur]

Description
After initialization, through UI or console (does not matter, because no errors are shown on both), the postman goes in a forever loading loop.
I tried to find any errors but nothing is shown except for the "Show DevToll (in current view)"

To Reproduce
There is no specific step to reproduce, because I've only updated the postman to the newest version.

Expected behavior
Postman to load and show UI normally.

Screenshots

App information:

• Native App
• Postman Version: 6.1.3
• OS: macOS High Sierra 10.12.6

[ghost]

Yes, I've also met with the same problem——The UI will be in the state of loading for quite a long time (about 5~10 minutes) each time. The UI is frozen:(

I'm running on the Win 8.1 SP1 (Simplified Chinese，x86).

Here's the screenshot after opening it, it still stays in frozen window....

Reinstalled but no help

[ilyaskhametov]

I experience the same problem after update. I also tried to reinstall Postman app, no luck. Have empty scree n with a spinner appearing each second near to the mouse pointer. Windows 8.1, Postman 6.3.1. Any help?

[RandomDude777]

Yep also getting this win 8.1

[Matriz88]

Same here, on win 8.1

If I try to open directly from command line (as suggested here) I get a lot of these logs:

[20260:0528/122727.995:ERROR:gles2_cmd_decoder.cc(9709)] [.DisplayCompositor-000000A96CBEF290]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering. [20260:0528/122728.000:ERROR:gles2_cmd_decoder.cc(17652)] [.DisplayCompositor-000000A96CBEF290]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIU M: invalid mailbox name [20260:0528/122728.000:ERROR:gles2_cmd_decoder.cc(9709)] [.DisplayCompositor-000000A96CBEF290]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering. [20260:0528/122728.000:ERROR:gles2_cmd_decoder.cc(17652)] [.DisplayCompositor-000000A96CBEF290]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIU M: invalid mailbox name [20260:0528/122728.000:ERROR:gles2_cmd_decoder.cc(9709)] [.DisplayCompositor-000000A96CBEF290]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering. [20260:0528/122728.000:ERROR:gles2_cmd_decoder.cc(17652)] [.DisplayCompositor-000000A96CBEF290]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIU M: invalid mailbox name [20260:0528/122728.000:ERROR:gles2_cmd_decoder.cc(9709)] [.DisplayCompositor-000000A96CBEF290]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering. [20260:0528/122728.001:ERROR:gles2_cmd_decoder.cc(17652)] [.DisplayCompositor-000000A96CBEF290]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIU M: invalid mailbox name [20260:0528/122728.001:ERROR:gles2_cmd_decoder.cc(9709)] [.DisplayCompositor-000000A96CBEF290]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering. [20260:0528/122728.001:ERROR:gles2_cmd_decoder.cc(17652)] [.DisplayCompositor-000000A96CBEF290]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIU M: invalid mailbox name [20260:0528/122728.024:ERROR:gles2_cmd_decoder.cc(9709)] [.DisplayCompositor-000000A96CBEF290]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.

[jemerald]

There is a work around discussed here, fixed my problem.
#4594 (comment)

[sivcan]

@siryur @RandomDude777 @MaleDong @Matriz88 @ilyaskhametov
The issue is related to Nvidia GPU's being used in some windows machines.
As mentioned by @jemerald, kindly follow this #4594 (comment) as mentioned by @harryi3t
We've released this fix with the 6.1.3 version so you wouldn't be needing the canary build.

In short,
Since you guys are already on 6.1.3, you've to make a new environment variable called POSTMAN_DISABLE_GPU and set it to true and it should work then.
Follow the steps in that comment and let us know if it works for you.

[ghost]

@jemerald & @siryur ：
Thanks to both of you! I did what you told us and everything seems going well with me again, the speed is very very fast than expected!

[RandomDude777]

@sivcan @jemerald @siryur: Much appreciate the fix guys! confirmed working.

[sivcan]

@MaleDong - Haha yes, we've made some major performance improvements!

Cool, so I'll close this issue then.

[siryur]

Well, that flag didn't do anything to my app... Things are running the same.
Although, using the PostmanCanary version resolved the thing without added the env var. Something happened here and I don't know what/why.

Well, if you want more information please tell me because I need to install the Postman app again.

[harryi3t]

@siryur Your issue is different than others who have commented in this thread.
Others were having an issue with the GPU. Adding that flag just disables it.
Unfortunately, the GPU issue got mixed up with yours.

Since the original issue you posted is different, I am reopening this.

• As of now, I don't know the cause of this issue. Did you jump between an old and the new version of Postman?
• Do you have all the data synced? If yes, you can delete/move the directory where Postman keeps the data. Warning: If you delete that directory any unsynced changed will be lost forever!

mv ~/Library/Application\ Support/Postman ~/Library/Application\ Support/Postman.bk

[Eli-Goldberg]

Same happens to me on Ubuntu when I tried 6.1.3,
it just doesn't work at all.
I can't find older versions of Postman so I can't use Postman at all now.

[ghost]

@Eli-Goldberg & @siryur ：

Here's the list of all kinds of versions, you can uninstall the latest one and reinstall a new one for a temporary fix until the official fixed this, hope this helps!

【For Linux】
1）https://dl.pstmn.io/download/version/6.0.10/linux64
2）https://dl.pstmn.io/download/version/6.0.10/linux32

【For Windows】
1）https://dl.pstmn.io/download/version/6.0.10/windows64
2）https://dl.pstmn.io/download/version/6.0.10/windows32

【For Mac】
https://dl.pstmn.io/download/version/6.0.10/osx64

[siryur]

Well, @Eli-Goldberg, I've solved my problem with the Postman Canary version. It worked like a charm 👍

As for the @harryi3t comment:

As of now, I don't know the cause of this issue. Did you jump between an old and the new version of Postman?

I'm not 100% sure, but I think I went from a 6.1.X to the 6.1.3 version. I'm not sure which of the previous version was, but I think I was in some 6.1 version.

Do you have all the data synced? If yes, you can delete/move the directory where Postman keeps the data. Warning: If you delete that directory any unsynced changed will be lost forever!

Yea, I've all my data synced (at least postman says it like that 😛 ).
I've deleted all my data previously and it had the same behavior. But I wasn't sure I've deleted that folder.
So, I tried it and it worked now.
Now, I'm not sure if it was me that didn't delete that folder or if it was something on server-side.

[harryi3t]

@siryur Glad that it worked! Closing this issue now

[kamilwlf]

I have this issue again

[blowsie]

I still have this issue