FSUIPC crashed (7.5.5a - beta version)

[kaha]

At the end of the flight, just short of touchdown in the Albatross. Didn't happen the first time, it crashed a few times also in different aircraft. But this time I'll report it. Please find the log and the ini file attached.

Karl

Crash_kaha.zip

[John Dowson]

Can you please also show me (or attach) the windows crash event (from the Event Viewer).

Did you get any crashes with 7.5.4 (or earlier versions), or is this only with 7.5.5a?

From the last lines in the log, it looks like FSUIPC was trying to close your lua threads:

Quote

...  
  5304375 LUA.13: L_Centurion21 send ONOFF
  5304437 LUA.13: L_Centurion21 send NAV
  5341125 Waiting for lua threads to process termination event....
  5343719 LUA: "C:\FSUIPC7\Lua\Elevator_Trim.lua": killed
  5402125 Waiting for lua threads to process termination event....

Why was this? What did you do to initiate the close of the lua threads/scripts? Why is there over a minute between the two 'Waiting...' log messages? What threads/scripts were being terminated?

[John Dowson]

Also, why are you auto-starting so many lua scripts with each aircraft? If they are aircraft specific (which many look to be), you should use profile-specific [Auto.xxx] sections (where xxx is the profile name).

[kaha]

23 minutes ago, John Dowson said:

Can you please also show me (or attach) the windows crash event (from the Event Viewer).

Did you get any crashes with 7.5.4 (or earlier versions), or is this only with 7.5.5a?

From the last lines in the log, it looks like FSUIPC was trying to close your lua threads:

Why was this? What did you do to initiate the close of the lua threads/scripts? Why is there over a minute between the two 'Waiting...' log messages? What threads/scripts were being terminated?

The crashes are only with version 7.5.5a

Here's the Windows log. Is this what you want to see?

 

I do not terminate autostarted scripts intentionally nor do I know of any code in my scripts that would terminate them. Maybe this is a message that shows FSUIPC is waiting for my event.terminate function? As an example please find my L_Centurion21.lua script in the .zip file. (This is a script handling a Centurion Autopilot hardware device). All my scripts use the event.terminate function. Some wouldn't need it (they just do a log line), but others do need it, like for closing open COM ports. I also include a normal .log file, it also has the same messages about waiting for lua threads to process termination event.....

From all 13 autostarted scripts only one is aircraft specific (L_B18_TankSwitch) and yes, you are right, I should and I will put it into the profile specific Auto section.

 

But, I have a thought: Could it be that this error message

  5158344 *** LUA Error: C:\FSUIPC7\lua\l_kaha_lua.lua:967: Error sending Input Event 'AS530_GPS_Outer'

causes the crash after some time?

Karl

[kaha]

11 hours ago, John Dowson said:

 

Forgot the .zip file.

 

Kaha.zip

[John Dowson]

12 hours ago, kaha said:

Here's the Windows log. Is this what you want to see?

Yes, but could you either copy and paste the exception details, or export it and attach the xml file. Its difficult for me to see the details in a screenshot, and I can't cut and paste the details I need (such as for translation!).

12 hours ago, kaha said:

But, I have a thought: Could it be that this error message

  5158344 *** LUA Error: C:\FSUIPC7\lua\l_kaha_lua.lua:967: Error sending Input Event 'AS530_GPS_Outer'

causes the crash after some time?

No, that won't be related - that indicates that you are trying to send an input event that doesn't exist.

12 hours ago, kaha said:

I do not terminate autostarted scripts intentionally nor do I know of any code in my scripts that would terminate them.

That is strange then and I wonder what is causing them to terminate.. I don't think the crash could cause the termination - I wouldn't expect the lua termination threads to be called if FSUIPC had crashed.

12 hours ago, kaha said:

Maybe this is a message that shows FSUIPC is waiting for my event.terminate function?

Yes, that is what those messages are showing. 

12 hours ago, kaha said:

The crashes are only with version 7.5.5a

Ok. I did say 'Note that this version contains some technical/non-functional updates that have not been fully tested yet, so if you get any other issues please let me know'!
Were you running the same lua scripts in 7.5.4 without issues then, or have you changed anything?
I will review the changes in 7.5.5a - but please can you show the the crash event details, either by pasting them or attaching the exported file.

Thanks,

John

[kaha]

Yes, I ran the same lua scripts in 7.5.4 and there was no crash.

Here are the crash details:

Protokollname: Application
Quelle:        Application Error
Datum:         03.09.2025 19:02:07
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      DESKTOP-038I96J
Beschreibung:
Name der fehlerhaften Anwendung: FSUIPC7.exe, Version: 7.5.0.5, Zeitstempel: 0x6889fb86
Name des fehlerhaften Moduls: FSUIPC7.exe, Version: 7.5.0.5, Zeitstempel: 0x6889fb86
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000010e970
ID des fehlerhaften Prozesses: 0x322c
Startzeit der fehlerhaften Anwendung: 0x01dc1ce7e553d8d7
Pfad der fehlerhaften Anwendung: C:\FSUIPC7\FSUIPC7.exe
Pfad des fehlerhaften Moduls: C:\FSUIPC7\FSUIPC7.exe
Berichtskennung: 81340e64-98bc-4125-a18e-013421650a06
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2025-09-03T17:02:07.1416366Z" />
    <EventRecordID>159821</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-038I96J</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FSUIPC7.exe</Data>
    <Data>7.5.0.5</Data>
    <Data>6889fb86</Data>
    <Data>FSUIPC7.exe</Data>
    <Data>7.5.0.5</Data>
    <Data>6889fb86</Data>
    <Data>c0000005</Data>
    <Data>000000000010e970</Data>
    <Data>322c</Data>
    <Data>01dc1ce7e553d8d7</Data>
    <Data>C:\FSUIPC7\FSUIPC7.exe</Data>
    <Data>C:\FSUIPC7\FSUIPC7.exe</Data>
    <Data>81340e64-98bc-4125-a18e-013421650a06</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Karl

[John Dowson]

Could you please set logging for Buttons & Keys, and show me the log the next time you get a crash. Also please attach your Elevator_Trim.lua script - this is not auto-ran but is just ran on a button press. I wonder why this was still running and had to be killed...

As this only started with 7.5.5, I may have to roll back each non-functional change one-by-one to see which, if any, provoke this crash. Looking at the changes, there is nothing obvious but they are quite technical and I may have removed something that I thought was unneded/used but actually is... These changes were related to device handling though, and ifthere were issues I would have thought they would be more common....

I will look into providing you with some updated versions to test.

John

[John Dowson]

Here's the first version to try: FSUIPC7.exe

[kaha]

The crashes don't appear often. I'll use the new .exe from now on.

Attached please find the Elevator_Trim script.

Elevator_Trim.zip

[John Dowson]

8 minutes ago, kaha said:

Attached please find the Elevator_Trim script.

Would be better and more efficient to also have that script auto-ran and modified to use event.param. Your assignments would need to be modified to use LuaValue instead of just Lua. As you have lots of assignments to this. would be easier to just do this by editing the ini - just change "CL16:R" to "CL16:V".

John

[John Dowson]

By the way, when the crash occurs are you repeatedly trying to adjust the trim? With the current script, if a trim button is pressed when the current script is running, it will be killed and a new script started. If you press repeatedly too fast, this is what could be happening (and why button press logging could help identify the issue). You can also use/adjust the LuaRerunDelay ini parameter to make sure the script is completed before being re-invoked, so you can also maybe try increasing this slightly, e.g. try 75 rather than 66.
This is not needed if you switch to event.param and LuaValue.

But for now, maybe keep it as it is while you try the new exe I posted.

John

[kaha]

10 minutes ago, John Dowson said:

Would be better and more efficient to also have that script auto-ran and modified to use event.param. Your assignments would need to be modified to use LuaValue instead of just Lua. As you have lots of assignments to this. would be easier to just do this by editing the ini - just change "CL16:R" to "CL16:V".

John

Ok, I will change it.

[John Dowson]

3 minutes ago, kaha said:

Ok, I will change it.

As I posted after this, maybe keep this for the time being just while you test the new exe...

You could also maybe test if this is the cause by repeatedly trying to trim to provoke a crash...

John

[kaha]

1 minute ago, John Dowson said:

By the way, when the crash occurs are you repeatedly trying to adjust the trim? With the current script, if a trim button is pressed when the current script is running, it will be killed and a new script started. If you press repeatedly too fast, this is what could be happening (and why button press logging could help identify the issue). You can also use/adjust the LuaRerunDelay ini parameter to make sure the script is completed before being re-invoked, so you can also maybe try increasing this slightly, e.g. try 75 rather than 66.
This is not needed if you switch to event.param and LuaValue.

But for now, maybe keep it as it is while you try the new exe I posted.

John

Yes, as you say it, I was changing trim continuously using my trim wheel. THe trim wheel turns a digital encoder, so button presses come rapidly.

If I understand you correctly I for now should not change to autorun the Elevator_Trim script but instead test with no changes running the new .exe file?

[kaha]

Ok, got it, I don't make any changes and test repeated trim changes.

[kaha]

It was an interesting test. When I was extensively using the trim wheel, throttle and ailerons I experienced the throttle and the ailerons (maybe FSUIPC in total) not responding for as long as up to 2 seconds. But then response was back and it didn't crash.

I will go on with this setup and do my normal flights.

[John Dowson]

4 minutes ago, kaha said:

When I was extensively using the trim wheel, throttle and ailerons I experienced the throttle and the ailerons (maybe FSUIPC in total) not responding for as long as up to 2 seconds.

Yes, interesting - I think continually killing and restarting lua threads can eventually cause issues (due to stack overflow issues). It makes me wonder if this is actually caused by any changes in 7.5.5 - maybe they just weren't noticed earlier, or execution is slightly slower for some reason causing a stack issue...

7 minutes ago, kaha said:

But then response was back and it didn't crash.

Was this with the latest exe I posted (7.5.5d), or the original 7.5.5a version? If the latest version, maybe retest with the older version and see if that crashes?

8 minutes ago, kaha said:

I will go on with this setup and do my normal flights.

Ok, let me know how it goes.

[kaha]

Yes with 7.5.5d

I'll retest with 7.5.5a

[kaha]

So I tested with 7.5.5a. Exact same behaviour. I probably just didn't notice.

Anyway, I'll go on with 7.5.5d and get back to you if it crashes.

Karl

[John Dowson]

1 hour ago, kaha said:

So I tested with 7.5.5a. Exact same behaviour. I probably just didn't notice.

Anyway, I'll go on with 7.5.5d and get back to you if it crashes.

Ok, please do. It would be good to know what is actually causing this crash!
When I get time, I will see if I can do anything with the crash event, but I find these difficult to use in 64bit apps...I will need to look into this further.

John

[John Dowson]

@kaha Could you use the attached exe instead please. This is exactly the same as the previous one except that it is a debug-enabled build.

It would be extremely useful if you could use this and also enable crash dump logs. To do this, see the following article: https://helgeklein.com/blog/creating-an-application-crash-dump/

If you are not familiar or happy editing the registry to do this, I can provide you with a .reg file that will add this for you.

John

FSUIPC7.exe

[kaha]

That's fine, I will do this.

Still log Buttons&Keys in addition?

Karl

[John Dowson]

53 minutes ago, kaha said:

Still log Buttons&Keys in addition?

Yes, I think that would also be useful.

John

[kaha]

Here's the log file when FSUIPC AND the sim freezed.

Karl

FSUIPC7_log.zip