Created attachment 122758 [details] weird display after clicking the save icon I've written a little Windows application in C++ using automation to create a simple spreadsheet and fill in values in regular intervals. Every minute or so the application calls SaveAsURL to store the document. After (more or less) two hours LibreOffice stops accepting the SaveAsURL command via COM/uno, but it still does accept the commands to enter a value - without updating the view. When the user then clicks the store-icon in the toolbar a weird error message pops up reading "Could not create system bitmap!" After a restart of LibreOffice the document is restored correctly, now showing the values entered after the StoreAsURL command has been refused. Maybe related to https://bugs.documentfoundation.org/show_bug.cgi?id=96607
Please attach the program or create macro to reproduce the bug easily. thanks
Created attachment 123118 [details] My code as requested by raal (The password is "LibreOffice") This is a rather old little Visual Studio 6.0 project I reactivated recently. Disaster occurs in CMeasDlg ::OnTimer () which is called every second. As you can see I have increased the interval for saving the document, so the document survives for at least one day of operation. The classes COooDesktop and COooCalc do the marshaling of the commands. The main dialog does a scan of all COM-ports and opens one CMeasDlg for each apparatus found. CMeasDlg creates a Calc sheet and waits for the user to click Start. Then the fun begins. In the beginning, when stored every ten seconds, LibreOffice crashed after about three hours. So you probably will have to wait for only 1000 storings instead of 5000 as I had estimated in the first place. HTH Peter
Comment on attachment 123118 [details] My code as requested by raal (The password is "LibreOffice") This is a rather old little Visual Studio 6.0 project I reactivated recently. Disaster occurs in CMeasDlg ::OnTimer () which is called every second. As you can see I have increased the interval for saving the document, so the document survives for at least one day of operation. The classes COooDesktop and COooCalc do the marshaling of the commands. The main dialog does a scan of all COM-ports and opens one CMeasDlg for each apparatus found. CMeasDlg creates a Calc sheet and waits for the user to click Start. Then the fun begins. In the beginning, when stored every ten seconds, LibreOffice crashed after about three hours. So you probably will have to wait for only 1000 storings instead of 5000 as I had estimated in the first place. HTH Peter
Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested information is provided.
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-20171030
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-20171204