https://bugs.documentfoundation.org/show_bug.cgi?id=165535

--- Comment #15 from Peter M <[email protected]> ---
I attached Visual Studio 2026 during this 120 sec freeze to soffice and pressed
the Break button. As I wrote earlier, there are two processes running during
this 120 sec period.

The first one is soffice.exe for which the call stack was:

win32u.dll!NtUserMsgWaitForMultipleObjectsEx()
soffice.exe!00007ff6919f4600()
soffice.exe!00007ff691a0745e()
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

The second one is soffice.bin:

ntdll.dll!NtWaitForMultipleObjects()
KernelBase.dll!WaitForMultipleObjectsEx()
combase.dll!DefaultWaitForHandles(unsigned long dwFlags=8, unsigned long
dwTimeout=250, unsigned long cHandles=1, void * * pHandles, unsigned long *
pdwIndex=0x00000044f9cefa58) Line 38
        at onecore\com\combase\dcomrem\sync.cxx(38)
combase.dll!CoWaitForMultipleHandles(unsigned long dwFlags=8, unsigned long
dwTimeout=250, unsigned long cHandles=1, void * * pHandles=0x00000044f9cefa50,
unsigned long * lpdwindex=0x00000044f9cefa58) Line 123
        at onecore\com\combase\dcomrem\sync.cxx(123)
sal3.dll!00007ffd00fc52b3()
mergedlo.dll!00007ffcd4377021()
salhelper3MSC.dll!00007ffd06de2ea1()
salhelper3MSC.dll!00007ffd06de2b08()
sal3.dll!00007ffd00fe8443()
ucrtbase.dll!thread_start<unsigned int (__cdecl*)(void *),1>()
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

I don't know if it's of any help. I'm a .NET developer, so I'm not experienced
with native code debugging. If there is anything else I can check, just let me
know.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to