I have had my K-Stars (From binary-factory latest version) closes for no reason during a session.

I could not find anything in the logs that would help point me in the right direction.

I found this on the Windows event viewer however: It does list the application faulted, but no details.

I recall there was an external logger for kstars at one point, is that still available? Thanks.


Faulting application name: kstars.exe, version: 0.0.0.0, time stamp: 0x64e7f5d8
Faulting module name: ntdll.dll, version: 10.0.22621.2134, time stamp: 0xeee69ec7
Exception code: 0xc0000374
Fault offset: 0x000000000010c239
Faulting process id: 0x0x35A0
Faulting application start time: 0x0x1D9D8ABA716CD27
Faulting application path: C:\Program Files\KStars Desktop Planetarium\bin\kstars.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 45c754aa-5117-4255-aeda-1c5d0b5a8c3a
Faulting package full name:
Faulting package-relative application ID:



Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: kstars.exe
P2: 0.0.0.0
P3: 64e7f5d8
P4: StackHash_a928
P5: 10.0.22621.2134
P6: eee69ec7
P7: c0000374
P8: PCH_E6_FROM_ntdll+0x000000000009F8A4
P9:
P10:

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_kstars.exe_3d627410ed9d38d3844d272f13e9db2945abcb_eea82fe1_a9f27e1d-29d3-40f4-846d-4ab065e1b11b

Analysis symbol:
Rechecking for solution: 0
Report Id: 309ac4ba-a997-4140-915d-d91dec3daac6
Report Status: 4
Hashed bucket:


Fault bucket 1236249459512947239, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: kstars.exe
P2: 0.0.0.0
P3: 64e7f5d8
P4: StackHash_a928
P5: 10.0.22621.2134
P6: eee69ec7
P7: c0000374
P8: PCH_E6_FROM_ntdll+0x000000000009F8A4
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d2795b6f-c942-4785-802b-4845fd6cd525.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_kstars.exe_3d627410ed9d38d3844d272f13e9db2945abcb_eea82fe1_a9f27e1d-29d3-40f4-846d-4ab065e1b11b

Analysis symbol:
Rechecking for solution: 0
Report Id: 309ac4ba-a997-4140-915d-d91dec3daac6
Report Status: 268435456
Hashed bucket: d045717a3afb400a51280a556009b227

I am going to add kstars.exe to the exploit bypass in Windows. I will see if that helps.

Crash Report

Looks like KDE has a bug that manifests as a crash:

KDE heap corruption is a bug in the KDE desktop environment that can cause programs to crash or become unstable. The bug occurs when a program allocates memory on the heap, but then fails to free it properly. This can lead to the heap becoming corrupted, which can then cause problems for other programs that are trying to use the heap.
There are a few things that can be done to fix KDE heap corruption. One is to update to the latest version of KDE. Another is to use a memory leak detector to find and fix the bug. Finally, it is also possible to disable the KDE heap manager altogether.
If you are experiencing KDE heap corruption, you should report the bug to the KDE developers so that they can fix it. In the meantime, you can try to work around the bug by using one of the solutions described above.
Here are some additional details about KDE heap corruption:
The bug is caused by a failure to free memory that has been allocated on the heap.
This can lead to the heap becoming corrupted, which can then cause problems for other programs that are trying to use the heap.
There are a few things that can be done to fix KDE heap corruption, including updating to the latest version of KDE, using a memory leak detector, or disabling the KDE heap manager altogether.
If you are experiencing KDE heap corruption, you should report the bug to the KDE developers so that they can fix it.

Hi @sonny486

Do you know, how to disable the KDE heap manager on Windows? I am experiencig the same issue with the latest Kstars on Windows.

BR,

Ladislav

Tapatalkkal küldve az én SM-G985F eszközömről

No, it's not the KDE heap manager, it's the Windows heap manager that calls the close.

I believe there is a bug in the KDE environment, don't know when it will get resolved. Crashes still happen on my Windows 11 box.

In Windows 10/11 if I go to Device security and go to core isolation and turn that off, it seems to stop KStars from crashing. I will keep an eye on mine tonight to see if it still crashes after, but it's been good for several hours not with that setting turned off.

Remember to restart your system after you make that change.

Let me know if anyone else sees an improvement.

Thanks.

Nevermind, it crashed, but took a lot longer to crash.

Windows system shut it down due to memory corruption.

Back to using KStars in a Ubuntu Virtual Machine on my Windows 11 box.