Qml Application freezes up after while (6 hours of execution)

[Delavega77]

A qml application after some hours of execution freezes (Windows says application not responding). It happens also when the application is idle. This happens both on windows 10 and windows 7. From the backTrace i got:

Thread 62142 (Thread 18716.0x370c):

0 0x00007ff9f36bc144 in ntdll!ZwWaitForSingleObject () from C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.

1 0x00007ff9f0938ba3 in WaitForSingleObjectEx () from C:\WINDOWS\System32\KernelBase.dll
No symbol table info available.

2 0x00007ff9aabbb816 in QUARTZ!AMGetErrorTextW () from C:\Windows\System32\quartz.dll
No symbol table info available.

3 0x00007ff9aaaca523 in QUARTZ!AMGetErrorTextW () from C:\Windows\System32\quartz.dll
No symbol table info available.

4 0x00007ff9f33b7bd4 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll
No symbol table info available.

5 0x00007ff9f368ced1 in ntdll!RtlUserThreadStart () from C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.

6 0x0000000000000000 in ?? ()
No symbol table info available. Backtrace stopped: previous frame inner to this frame (corrupt stack?)

the backtrace is similar for all threads. Is something related to ntdll? thank you

[raven-worx]

@Delavega77 said in Qml Application freezes up after while (6 hours of execution):

Thread 62142 (Thread 18716.0x370c):

thread 62142...rly?!?
seems your application is more busy switching threads than actually executing threads?

[Delavega77]

@raven-worx
The entire stacktrace shows more or less 20 threads, don’t know why some threads have these huge number.
In my application i create 4 threads, and i supposed that those threads were created from a library that the application uses. Could it be? Thx

[JonB]

@Delavega77
@raven-worx may know more than I.

However, it seems to me: errors which show in ntdll.dll are not usually meaning it itself is messed up, just that's where things show up.

If I understand the stack correctly, it looks like you are in quartz.dll (what's that?) and it is trying to get Windows system error text. Implying to me something has gone wrong and it's trying to report it, and that's where the crash happens. I'm not sure why QUARTZ!AMGetErrorTextW is calling WaitForSingleObjectEx (), but maybe something cross-thread needs waiting on?

I'd want to find out what quartz.dll (https://www.processlibrary.com/en/directory/files/quartz/24420/) is all about....

[raven-worx]

@Delavega77
maybe a (very) long shot, but maybe updating the graphic card drivers might help implicitly

[Delavega77]

@raven-worx
@JonB
Thank you for your reply. The strange thing is that this happens always after the same amount of time either the application is doing something or it is idle.
This application has a lot of graphics stuff( video and sounds).
It happens on different pc with different windows (7/10 ) and different chipset from xeon,i5 till old core duo duo, with different graphics card, radeon and nvidia 710/210/quadro.
Thanks for your support