This bug was filed from the crash reporting server and is br-206a6bdc-1fc7-41bd-98fb-ce63594e52bc. ========================================= It crashes constantly when I try to open the save dialog to save an untitled document. I'm running Windows 10 64 bit. Sorry if I'm not doing something right with this report. Your bug report system is really confusing.
What is your version of LibreOffice ? Set status to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF
Version info added.
(In reply to wonderpix from comment #2) > Version info added. Thank you. Crash report -> NEW
Hello, Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test?
Could you give a try to last stable LO version 5.4.4? (+ as Xisco suggested, rename your LO directory profile: see https://wiki.documentfoundation.org/UserProfile#Windows) Searching about NahimicMSIOSD.dll, I found info here: https://bugzilla.mozilla.org/show_bug.cgi?id=1233556 It seems there's some bug on this dll. For the test, could you: - uninstall current Nahimic - uninstall current audio driver - install new audio driver - install new Nahimic (as https://bugzilla.mozilla.org/show_bug.cgi?id=1233556#c54 suggested) Michael: I noticed that Firefox patch was to blacklist the dll, do you know if the mechanism exists on LO? (I mean for other dlls than those which concern OpenGL and OpenCL) Notice that, still according to the link, it seems that A-Volute (the company who created Nahimic) hadn't version their driver so if even we can blacklist the driver, we may not specify versions.
Looking at http://crashreport.libreoffice.org/stats/signature/NahimicMSIOSD.dll, it seems we don't have crashes for 5.3.7 or 5.4.4. Should be put it to RESOLVED WORKSFORME instead? I guess it was wrong to move it to NEW in the first place as no one else could reproduce it, but now, it's also wrong to move it to NEEDINFO from NEW
So lets close this; nice catch Xisco =) unfortunately catching bad components on a windows system and avoiding them is not super-easy; but I'm glad that something stopped us mis-interacting in this way these days. At least - until we have data that says otherwise, lets shut this. Thanks for filing Wonderpix ! and sorry for the confusion filing.