Created attachment 141076 [details] PoweShell code to crash libreoffice Here is Crash Reports: http://crashreport.libreoffice.org/stats/crash_details/c49ef0b4-cedd-4d66-b330-0aa30efd5fa9 http://crashreport.libreoffice.org/stats/crash_details/b1102efc-94e6-4a2a-96c5-7a7022a52b5f When i run either PowerShell.txt or vba.txt the LibreOffice crashes. Note: - PowerShell.txt takes significant more time to crash than vba.txt. - I have not managed to crash LibreOffice when using the built in LibreOffice Basic. -- So you need external VBA get LibreOffice crash. Example SolidWorks VBA.
Created attachment 141077 [details] VBA to crash LibreOffice
Also crashed it when using VBA from Microsoft office 2000 macros. http://crashreport.libreoffice.org/stats/crash_details/e1bbf109-7483-4e42-87e6-b05a5512c0e9
Can you reproduce the crash with version 6.0.3? Or perhaps a master build, if you don't want to upgrade yet (it installs separately): https://dev-builds.libreoffice.org/daily/master/Win-x86_64@42/current/ I see the other signature has a report for 6.0.2, but the other only has reports for 5.x.
(In reply to Buovjaga from comment #3) > Can you reproduce the crash with version 6.0.3? Or perhaps a master build, > if you don't want to upgrade yet (it installs separately): > https://dev-builds.libreoffice.org/daily/master/Win-x86_64@42/current/ > > I see the other signature has a report for 6.0.2, but the other only has > reports for 5.x. Hi, Yes i can: http://crashreport.libreoffice.org/stats/crash_details/762bb1fc-60e4-4675-9322-bc3037c62130
Ok, so your PowerShell script is creating and closing Calc documents 3000 times. I tested it. 1. Launched PS 2. set-executionpolicy remotesigned 3. .\powershell.ps1 (I had renamed your file) My crash report is here: https://crashreport.libreoffice.org/stats/crash_details/49ac0ea1-2e30-496f-8198-e02c9e5632a9 Version: 6.0.3.2 (x64) Build ID: 8f48d515416608e3a835360314dac7e47fd0b821 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: fi-FI (fi_FI); Calc: group
Dear matti.jaatinen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
We don't have more crash reports from LibreOffice 6.1 nor LibreOffice 6.2 in https://crashreport.libreoffice.org/stats/signature/ToolBox::SetItemBits(unsigned%20short,ToolBoxItemBits) Dear matti.jaatinen@norelco.fi, 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'.
Dear matti.jaatinen, 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
Dear matti.jaatinen, 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-FollowUp