The title pretty much says it all: running the "Network" example app is causing the simulator to crash at the exact moment that server.py sends the "PONG" response over TCP. I have repeated this four times in a row with the same result.
I'm running the simulator on OS X (M2 processor, Sequoia 15.4.1).
I would like to include the "problem details" provided when re-opening the simulator, but they exceed the character limit for posts. If anyone has a suggestion for how to edit it down, I will do so. I believe based on the behavior that this is slightly different (or at least less complicated) than the issue raised in this post.
The only thing I can think of to test is whether it's somehow the pdx build. Does this one do the same thing?
What's happening is there's a race between the server closing the connection and the code, and if it happens in the wrong order (which is pretty random) it causes a NULL dereference. We'll have 2.7.3 out as soon as we can!