GRplugin Crash after closing outbound window

Chriss Klosowski (1306415)

Hello!

We’ve received several reports from our controllers regarding a plugin issue where it crashes after closing the outbound windows. Regardless of the departure runways selected, the plugin appears to open all available runways for the specific field. When controllers attempt to close these runways, the plugin crashes.

The following error message is displayed in EuroScope:
Error: Unhandled exception in plug-in: Ground Radar plugin. Plug-in is unloaded.

Juha Holopainen (839337)

I'm assuming you've set up the plugin to open the window(s) in the plugin's settings file and they're not opening completely by themselves? Could I have a look at the settings?

Chriss Klosowski (1306415)

Hello, you can find the source code on this link: https://github.com/Arabian-vACC/OMAE-U.A.E-FIR-Controller-Pack/commit/a3d4a2557f6669e9f2783d5b1b32142b6487fbb4 this is the last change that we did that stopped the crashes.

You can find the full GRpluginSettings.txt here: https://github.com/Arabian-vACC/OMAE-U.A.E-FIR-Controller-Pack/blob/main/OMAE/Plugins/Ground%20Radar%20Plugin/GRpluginSettings.txt

Initially, we configured the outbound list to display by default for each airport, as we rely on the GRPlugin timer instead of alternative timers. The issue arises at airports like Dubai, where the outbound list opens for all runways (e.g., 12L/12R/30L/30R). This forces controllers to close four separate lists, and the plugin crashes after closing the third one.

Juha Holopainen (839337)

Regarding the plugin opening the list for all runways, your settings file had "List_Outbound=*,1,100,800". That specifies all lists to be opened, so that part was working correctly. To open the lists only for active departure runways, change the bolded 1 to 2 instead.

For the crash, I have not been able to reproduce it (I've tried opening the lists both using the setting you had and manually, but in both cases I've been able to close the lists without a crash). Is there some specific sequence of steps you can think of that need to be done to trigger it, or is it supposed to happen every time when closing the lists?

Chriss Klosowski (1306415)

Juha Holopainen (839337)

Our controllers have reported that after switching from an ASR back to the GRplugin ASR and then closing the list I guess quite quickly it will crash the plugin. That is what was reported by our controllers.

Juha Holopainen (839337)

I've now been able to replicate a crash related to closing the lists, however it doesn't seem to be related to the setting or switching ASRs - at least I haven't been able to come up with a sequence of steps that would link either of those to a subsequent crash when closing the lists.

What does seem to cause a crash is trying to close the lists too quickly, i.e. clicking the left mouse button successively fast enough for it to be recognized as a double-click instead of multiple single clicks. The crash happens regardless of how the double-clicked list had been opened (manually from the menu bar or automatically using a setting) and the number of lists currently open (even with only one list open, the plugin will crash if the close button is double-clicked). I'll fix this for the next release, until then the lists need to be closed with care - avoiding double-clicks.