This report indicates GSX has supposedly being the cause of a problem, but it's not. Even if the crash can be reproduced and "fixed" by not using GSX, but that's not because GSX is the cause of the problem or there's anything we can fix.
Yes, I agree there's something which might be related to the usage of the Simconnect menu. I'm calling it "Simconnect menu", in order to clarify what it is. It's NOT the "GSX menu". That menu is handled entirely by the sim, and Simconnect apps don't have *any* control over it.
And, there IS something strange with that menu, which happens only with some 3rd party airplanes, and is that it gets resized automatically in a strange way ONLY after loading one of such airplanes. We don't know what is causing this, and why it happens when loading some planes and not when loading other planes.
Again, we don't have any control over its appearance, placement, size, etc, from GSX. It's done entirely by the sim.
So, if someone noticed some that problem in conjunction with using GSX, it's might simply caused by the fact that, it's the MENU itself which is leaking, or that doing what whatever it is those 3rd party airplanes are doing which cause the menu to be resized when they load, might have been triggering some kind of bug in P3D, which will happen ONLY after a long flight and only after having ANY application that opened that menu.
Since the Simconnect menu it's an internal system of the sim, it can surely crash it. GSX, running entirely external to it, under the Couatl interpreter, cannot cause such CTD, especially something that seems to be happening out of the blue, without even interacting with it, which seems to be a memory leakage problem.
It's possible the fact that restarting Couatl would fix the problem, because when a Simconnect client disconnects and reconnects, the sim might do some internal cleanup of the resources related to the menu too.
It would be interesting to do the same test with another Simconnect app that use the menu, like SODE for example.
What I really cannot explain, instead, is the supposedly geographical relationship to the crash, as if this leakage was also related in some way with the scenery. Possibly, in order to crash, the two issues must happen together, so it would be helpful to know which scenery is installed, or if it happens even with the default scenery only.
