Created attachment 121447 [details] Test with queryEmptyCells method I tested the attached file in which I use the queryEmptyCells method on a single line range. This file works perfectly with the 5.0.4.2 x86 version. Version: 5.0.4.2 Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78 Locale : fr-FR (fr_FR) But with the lo 5.0.4.2 x64 version, Version: 5.0.4.2 (x64) Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78 Locale : fr-FR (fr_FR) We have some strange results : - SEH access violation message. - complete crash of LO. - When we try to manage step by step with the EDI, after the queryEmptyCells call, the subroutine Main continues until the end. - and others... I confirm that after each new installation, I use the correct JAVA 1.8.0.66 for x86 or x64 depending the Lo x86 or x64 version. OS : Windows 8.1 x64 (Intel i5 processor).
crash with 5.0.4.2 (x64) ID sestavení: 2b9802c1994aa0b7dc6079e128979269cf95bc78 and Version: 5.2.0.0.alpha0+ (x64) Build ID: cfe08df695c046371c4361a434176e6381e3e064 CPU Threads: 1; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-12-15_13:10:55 error message appears: com.sun.star.uno.Exceptioncom.sun.star.configuration.ConfigurationProvider expects a single, non-empty, string nodepath argument BASIC runtime error. Object variable not set. after few hits of button in testing document file crashes.
If possible, please follow the instructions provided at this link < https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg > and submit a backtrace.
Created attachment 121546 [details] Bactrace with LO x64 and java x86
Created attachment 121547 [details] Backtrace with LO x64 and java x64
Created attachment 121548 [details] Backtrace when using EDI
Please find enclosed the required backtraces. The first backtrace is generated with LO x64 and java x86 version. The second backtrace is generated with LO x 64 and java x64 version. The third backtrace is generated when using the EDI and manage the execution step by step. I stopped the Windbg program and made an analyze. I expect these files will help you.
For your information, I installed today on my computer the version : Version: 5.1.0.1 (x64) Build ID: bcace328aabc4c8c10b56daa87da0a2ee6579b5a Threads 4; Ver: Windows 6.29; Render: GL; Locale : fr-FR (fr_FR) And I tested the first file "Test with queryEmptyCells method". Results : no access violation, no Calc crashes and good functionnality with the EDI. I expect this will help you.
(In reply to ThierryT from comment #7) > For your information, I installed today on my computer the version : > > Version: 5.1.0.1 (x64) > Build ID: bcace328aabc4c8c10b56daa87da0a2ee6579b5a > Threads 4; Ver: Windows 6.29; Render: GL; > Locale : fr-FR (fr_FR) > > And I tested the first file "Test with queryEmptyCells method". > > Results : no access violation, no Calc crashes and good functionnality with > the EDI. > > I expect this will help you. So probably something that got fixed between LO 5.0 and 5.1? Setting as WORKSFORME on the basis of the above information provided by the original reporter.