Thanks for the feedback. Good to know.

Anyway, I ran into a bunch of crashes when flying yesterday and found the issue in code that was introduced around 3.0.2. Happened when trying to display the tooltip for the aircraft trail. One crash less at least.🙂

I also fixed another one that appeared randomly when reading the MSFS scenery library. Also quite an old one.

I hope to have a 3.0.7.rc1 available soonish (or so, need more testing).

Alex

 

Sadly, it seems starting to pick up frequency again, even on 3.0.9, same Qt5Gui.dll CTD as before...

It literally start much infrequent when starting this new profile and now picking up speed, crash almost daily as before...

https://drive.google.com/file/d/1NlRCkjam5S1NdX6tQhOAAsiZbFek6bn0/view?usp=sharing

57 minutes ago, C2615 said:

Sadly, it seems starting to pick up frequency again, even on 3.0.9, same Qt5Gui.dll CTD as before...

It literally start much infrequent when starting this new profile and now picking up speed, crash almost daily as before...

https://drive.google.com/file/d/1NlRCkjam5S1NdX6tQhOAAsiZbFek6bn0/view?usp=sharing

Sorry, cannot download the report. Can you send it by email (https://albar965.github.io/contact.html) or use a better cloud sharing service like https://filetransfer.io/?

Alex

Thanks for the files @C2615. Unfortunately there is no stacktrace included for some reason. This would allow me to find the exact place of the crash.

Where do you get the Qt5Gui.dll information? Is this some DrWatson stuff? Maybe this prevents the stack trace generation.

Alex

17 hours ago, albar965 said:

Where do you get the Qt5Gui.dll information? Is this some DrWatson stuff? Maybe this prevents the stack trace generation.

It's in the app crash events of windows' event viewer:

Faulting application name: littlenavmap.exe, version: 0.0.0.0, time stamp: 0x66a91ae1
Faulting module name: Qt5Gui.dll, version: 5.15.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x004ef5b4
Faulting process id: 0x0x680C
Faulting application start time: 0x0x1DB05BDFC7AB7BE
Faulting application path: N:\FS\N\LNM3\littlenavmap.exe
Faulting module path: N:\FS\N\LNM3\Qt5Gui.dll
Report Id: 0d9093a7-0f4d-425d-aceb-ac2ff16caa2e
Faulting package full name: 
Faulting package-relative application ID: 



- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> 
  <EventID>1000</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2024-09-13T10:08:13.0105114Z" /> 
  <EventRecordID>44619</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="30216" ThreadID="30264" /> 
  <Channel>Application</Channel> 
  <Computer>Umi</Computer> 
  <Security UserID="S-1-5-21-1507506471-1515142045-11927022-1001" /> 
  </System>
- <EventData>
  <Data Name="AppName">littlenavmap.exe</Data> 
  <Data Name="AppVersion">0.0.0.0</Data> 
  <Data Name="AppTimeStamp">66a91ae1</Data> 
  <Data Name="ModuleName">Qt5Gui.dll</Data> 
  <Data Name="ModuleVersion">5.15.2.0</Data> 
  <Data Name="ModuleTimeStamp">00000000</Data> 
  <Data Name="ExceptionCode">c0000005</Data> 
  <Data Name="FaultingOffset">004ef5b4</Data> 
  <Data Name="ProcessId">0x680c</Data> 
  <Data Name="ProcessCreationTime">0x1db05bdfc7ab7be</Data> 
  <Data Name="AppPath">N:\FS\N\LNM3\littlenavmap.exe</Data> 
  <Data Name="ModulePath">N:\FS\N\LNM3\Qt5Gui.dll</Data> 
  <Data Name="IntegratorReportId">0d9093a7-0f4d-425d-aceb-ac2ff16caa2e</Data> 
  <Data Name="PackageFullName" /> 
  <Data Name="PackageRelativeAppId" /> 
  </EventData>
  </Event>

As before, the crash is very sudden, lnm just vanished in the middle of flight, or after the flight when it's parked in the background, without any input change.

Edited September 14, 20241 yr by C2615

I need the file "little_navmap_stacktrace.txt" in a report to find the source of the crash. This is missing for some reason in all your reports. No idea why. 

Let me know whenever the stack trace appears in a crashreport.

I suppose something is wrong with your system because I've got only one crash reported for 3.0.9 so far and this was a quick fix thanks to the stack trace file.

Alex

Just quick update, I haven't have any crash since Oct.21st, I do have one on 3.0.11 at that date, but never since, and I run it just like normal, almost every day.

And that newest crash report still don't have stacktrace, so IDK... I don't have any significant system changes, maybe the 3.0.11 is the cure?

I'll try 3.0.12 this weekend and see.

BTW is the autosave of flight trace implemented? not see it on changelog, and not have a crash to verify for few weeks

Edited November 7, 20241 yr by C2615

52 minutes ago, C2615 said:

Just quick update, I haven't have any crash since Oct.21st, I do have one on 3.0.11 at that date, but never since, and I run it just like normal, almost every day.

Glad to hear. 👍

53 minutes ago, C2615 said:

And that newest crash report still don't have stacktrace, so IDK... I don't have any significant system changes, maybe the 3.0.11 is the cure?

Crashreports should always appear for a not clean shutdown. Strack trace is a different story. On some systems it does not show up.

3.0.11 fixed a lot of issues (also crashes) and 3.0.12 a few more.

55 minutes ago, C2615 said:

BTW is the autosave of flight trace implemented? not see it on changelog, and not have a crash to verify for few weeks

No. I might consider this for future updates but I'd rather have crashes fixed.🙃

Alex