Closed qa-nowsecure closed 2 years ago
@qa-nowsecure Can you confirm that you experienced this problem when running the app on a M1 Mac using Rosetta? The logs seem to be pointing at that, so I'll link it to this issue tracking proper M1 support.
Hi, At the bottom of the logs, it says that the device is a MacBookPro16 running a Quad-Core Intel Core i5, 1.4 GHz and not an Apple M1 chip.
@jviotti I don't think this issue is related to the compatibility issues with the Apple M1 chip.
@rishitc True, however the stack trace seems to originate at a Rosetta shared library and the exception is EXC_BAD_INSTRUCTION
, which might be more probable on a M1 machine due to the instruction translation layer. I also checked on my Intel Mac, and I don't seem to have a libRosetta
shared library anywhere.
Could it be that the Rosetta layer results in the stack trace reporting a fictitious Intel Mac model? It might be worth validating that hypothesis.
@rishitc do you know of a way to reproduce this crash?
We don't have any debugging symbols for this version of Postman, so I'll close the issue for now. Feel free to open another issue if you come across the same crash on the latest versions of Postman (we have debugging symbols for those and we'll be able to help you out there), thanks!
Environment Information
Screenshot
Problem Details