Bug 166290 - Large number of soffice.bin crashes captured
Summary: Large number of soffice.bin crashes captured
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
25.2.2.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-21 23:53 UTC by Michellehdr
Modified: 2026-01-27 12:38 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Stack info (4.42 KB, text/plain)
2025-06-26 19:47 UTC, Michellehdr 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michellehdr 2025-04-21 23:53:17 UTC 
Hash ID: 9d16010e-bfb3-a863-1a23-36325e0e4aa0
Windows 11/10
soffice.bin 25.2.2.2/ 25.2.1.2/ 25.2.0.3/ 24.8.5.2
Comment 1 V Stuart Foote 2025-04-22 00:37:13 UTC 
Nothing actionable here. Please provide specifics, and perhaps post up representative CrashDump .dmp files.
Comment 2 Michellehdr 2025-04-23 17:39:43 UTC 
@V Stuart Foote, is it safe if I paste stack info here?
Comment 3 V Stuart Foote 2025-04-23 19:14:44 UTC 
Sure, you can pick up the mini-dumps from:

C:\Users\<username>\AppData\Local\CrashDumps

Use the 'Add an attachment' link above and attach--rather than copy/paste and we can review it with Windows SDK debug tools and appropriate debug symbols.

Alternatively, you can install the Windows SDK for the WinDbg tool and link to the MS and LibreOffice debug symbols.  Steps to set up and generate a stack trace with symbols as here:

 https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Comment 4 Michellehdr 2025-06-26 19:47:06 UTC 
Created attachment 201497 [details]
Stack info
Comment 5 V Stuart Foote 2025-06-26 20:47:51 UTC 
Thanks for posting the stack trace, unfortunately without windbg link to a symbols store nothing really of use.

Also, could you please describe what processing you were doing with LibreOffice when the crashes have occurred, presumably LO multiple releases 24.8.5.2 -> 25.2.2.2

Just guessing, but was there a macro/extension being run, suggested by the unoidllo note in the trace?
Comment 6 Michellehdr 2025-06-30 17:46:29 UTC 
Thanks for you reply. This bug was captured by MS telemetry system. I don't have any details on repro steps, machine info, etc. I reported this issue is to draw your attention to see if you see similar issue or you got any feedback from end users about this? The information I shared previously is everything I have. Please  let me know what else I can help. Thanks!
Comment 7 Michellehdr 2025-07-09 21:50:09 UTC 
Hi team, I would like to follow up with you about this bug. Is there any update?
Comment 8 Michellehdr 2025-08-11 23:10:24 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2025-11-25 15:38:45 UTC Comment hidden (obsolete)
Comment 10 Buovjaga 2026-01-27 12:38:05 UTC 
(In reply to Michellehdr from comment #6)
> Thanks for you reply. This bug was captured by MS telemetry system. I don't
> have any details on repro steps, machine info, etc. I reported this issue is
> to draw your attention to see if you see similar issue or you got any
> feedback from end users about this? The information I shared previously is
> everything I have. Please  let me know what else I can help. Thanks!

Without repro steps or a backtrace with symbols, nothing can be done. When a crash happens, normally LibreOffice asks, if you want to submit a crash report to https://crashreport.libreoffice.org/ What about in this case?