User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10240 Build Identifier: LibreOffice 5.1.0.0.alpha1 (x64) LibO WINx64 crashes by using the macro-tool XRAY in a Macro. This problem doesn't exist by using LibO 5.x WINx32 or Linuxx64. So it seems to be a problem with WINx64. Reproducible: Always Steps to Reproduce: 1. Installing XRAY 2. put in a macro: xray thisComponent 3. Start the macro Actual Results: LibO crashes with no device. (The Macro without "xray thisComponent" works fine) Expected Results: Open a Dialog and obviously no crash. [Information automatically included from LibreOffice] Locale: de Module: StartModule OS: Windows 10 Home OS is 64bit: yes LibO WINx64 Reset User Profile?No
can confirm Bug on Windows Builds 5.0.3.2 64bit only. No crash with 32 builds. I have dived a little bit deeper into the rproblem and try to isolate the problem. First I isolate the first crash: if Len(allPropsNames) = 0 then ' only once per current object for x = 0 to xMax ' each property or pseudo-property info2 = info1(x) allPropsNames = allPropsNames & "£" & info2.Name & "£" ' build list £name1££name2££name3£ etc next end if My first idea was, that the string-len will extend, but doing it step by step the string length only arrives around 4000. By putting a massagebox inside of the if .. end if code, i generate a errormessage before crash (see screenshot). But I guess, this is not the only problem.....
Created attachment 120326 [details] Error message just before crash
NEW per comment 1. Backtrace would be nice: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Does this still happen with recent LO versions?
needinfo as of comment 4.
I "restarted" using the tool yesterday. Till today all was okay. I even used it in python scripts. Suddenly today it started crashing. First xray (with a small x) was not recognized as function. I used Xray and it worked once. After that even the caller function was not recognized as function. (I mean the function A which was calling function B that has a line with xray) Restarted the computer. Reinstalled xray. Same problem. PS. I do not know know if this has some importance but yesterday I "saved" "Panel Xray with current dimensions" and also changed fonts. After that it worked as expected (till today, about one hour ago). (UBUNTU 14.04, x64, Cinnamon desktop)
Ηλίας: could you try with LibreOffice 5.2?
https://wiki.documentfoundation.org/Installing_in_parallel/Linux or https://launchpad.net/~libreoffice/+archive/ubuntu/ppa
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-20170131
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-20170328