Description: Hello, we use LibreOffice CALC to automatically generate ODS files in a web application running in IIS (Windows Server 2016 in a VM) For this purpose we use the LibreOffice SDK and the CLI component. The component addresses the LibreOffice CALC application installed on the server side. Since version 7.0, we get the error "Binary URP bridge already disposed" if we repeatedly address LibreOffice. But this error occurs only up from the second call. With LibreOffice 6.4.6, this error did not occur. Furthermore, the error does not occur in version 7.0 if the web application is not running in IIS but in the VisualStudio development environment (with IIS Express). We suspect a bug in LibreOffice 7.0 here. We have identified the following manual workaround: - Starting LibreOffice CALC on the server - Now the web application generates an ODS file via the CLI component - While the web application creates the ODS file (here our web application shows a permanent waiting bar), the previously started CALC instance on the server is terminated - The creation of the ODS file is now successfully continued - For future calls the error will no longer occur If the workaround is not executed, the above error message is displayed after a few seconds up from the second call. Many greetings, Marc Actual Results: Error "Binary URP bridge already disposed" appears. Expected Results: No error appears Reproducible: Always User Profile Reset: No Additional Info: see Description
@Mike I think you're knowledge is needed here.
Smells like LibreOffice crashing (or otherwise unexpectedly terminating - but c.f. bug 102274). Any chance to stick a debugger to the LibreOffice process inside the IIS session? Assuming that it _does_ terminate there somehow.
Although we were not able to debug LO, we did some further analysis: It seems that the method "terminate" of the interface "XDesktop" does not fully terminate the LibreOffice instance. After the terminate command the LO-instance does have high CPU usage and hangs up. The result of the terminate-method is "true", however. The next "bootstrap"-call will not start a new instance of LO. Only after the "old" LO instance is terminated manually (via task manager) the new instance will start. If the "terminate" method is not used at all, the mentioned error message will appear. Additional note: in our use case the complete process is triggered by a web service (in IIS).
Hello Marc, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Bugs seems to be fixed in LibreOffice 7.2.2.2 --> Changed to 'Resolved'. Thanks a lot for fixing.