Odd behavior within CryptoError on some windows machines. My laptop has this issue but my desktop does not.
This issue may be either CryptoError somehow returning despite [[no_return]] or odd behavior with the thrown exception.
Neither should be a problem. CryptoError always throws and cannot return, so if it returns, that is an installation specific bug. If the thrown exception is not caught, then that is another installation specific bug because it is definitely within a try/catch.
More investigation will be needed, especially since my debugger is limited on that platform.
P.S. If the community will offer their machines, it may help track down the root cause.
Odd behavior within CryptoError on some windows machines. My laptop has this issue but my desktop does not.
This issue may be either CryptoError somehow returning despite [[no_return]] or odd behavior with the thrown exception.
Neither should be a problem. CryptoError always throws and cannot return, so if it returns, that is an installation specific bug. If the thrown exception is not caught, then that is another installation specific bug because it is definitely within a try/catch.
More investigation will be needed, especially since my debugger is limited on that platform.
P.S. If the community will offer their machines, it may help track down the root cause.