Writer crashes on close everytime I open a document, manually or programmatically, after having created an instance of a MailMerge object using CLI-uno. Step to reproduce: - Create a small C# app that does the following: XComponentContext context = Bootstrap.bootstrap(); XMultiServiceFactory msf = (XMultiServiceFactory)context.getServiceManager(); //Create the Mail Merge service object mailMerge = msf.createInstance("com.sun.star.text.MailMerge"); ((XComponent)mailMerge).dispose(); //Open document XComponentLoader componentLoader = (XComponentLoader)msf.createInstance("com.sun.star.frame.Desktop"); componentLoader.loadComponentFromURL(new Uri(System.Environment.CurrentDirectory + @"/test/test1.odt").AbsoluteUri, "_blank", 0, new PropertyValue[] { }); - Close writer. - You receive an error. Inside Event Viewer you find: Faulting application name: soffice.bin, version: 5.0.4.2, time stamp: 0x566ad0aa Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6 Exception code: 0xc0000409 Fault offset: 0x000a7666 Faulting process id: 0x16ac Faulting application start time: 0x01d14e13f3c4a8e4 Faulting application path: C:\Program Files (x86)\LibreOffice 5\program\soffice.bin Faulting module path: C:\Windows\SYSTEM32\MSVCR120.dll Report Id: 3559a71e-ba07-11e5-82a8-68f72874dcaa Faulting package full name: Faulting package-relative application ID: The same error is thrown even if you open a document manually, without using loadComponentFromURL but keeping the test program opened.
Created attachment 121900 [details] Test project. Added test project. I forgot to say that, as a workaround, it's possible to enable QuickStart. With QuickStart enabled the problem doesn't come out.
Could you get a backtrace: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
@Meeks, @Kendy, @JMux: Any ideas how this can be moved forward, as the project file the user submitted requires MS Visual Studio in order to run.
(In reply to Yousuf (Jay) Philips from comment #3) > @Meeks, @Kendy, @JMux: Any ideas how this can be moved forward, as the > project file the user submitted requires MS Visual Studio in order to run. As beluga already pointed out, we need a backtrace. I don't have any Windows environment. OTOH there is a mail merge backtrace attached to bug 96914, which I see on closing LO Writer 5.0, so this might actually be related. The attached bt is completely unrelated to my reported bug 96914, but I stumbled over it why analysing the bug. Still a Windows bt would help to clarify.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20161010
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20161108