This bug was filed from the crash reporting server and is br-3915ecfe-e709-4058-b077-66e284b93bf8. ========================================= Steps to reproduce the crash: 1. Start Calc with new document 2. Enter e.g. 1 into cell A1 3. Crash
Software Download was from https://dev-builds.libreoffice.org/pre-releases/win/aarch64/ Version 7.4.7.2
Could you give a try with LO 7.5.4 ? I mean even if we confirm the bug with 7.4.7, this version is last one from 7.4 branch. If it doesn't work, you may also dev version 7.6.0 but this one is obviously just for testing not for production use.
Hello, as recommended I have installed LO 7.5.4.2 and can confirm that the bug still exists. The new crash report can be fould here: https://crashreport.libreoffice.org/stats/crash_details/5d013ac7-f28c-4af7-afe1-a2a61197b558 Please let me know if I should install the beta1 (or the latest nightly build) of LO 7.6.0 and try it again.
Thank you for your feedback. "Version" field must correspond to the earliest when the bug has been encountered so I reverted back the version. Yes giving a try to a 7.6 may be useful since https://cgit.freedesktop.org/libreoffice/core/commit/?id=ef533553559fe09b4afab651fc692885d1acf4ed (from January 2023) is on 7.6 branch but not cherry-picked on 7.5 branch (I suppose because it wasn't bugtracker related). At least, I'm pretty sure if there's still a crash, it should be a bit different since bridges\source\cpp_uno\msvc_win32_arm64\cpp2uno.cxx has been modified with this patch.
I also installed LO 7.6.0.0 beta1 for Windows (arm64) and I have to confirm that this crash still happens in Calc if you just begin to enter a simple content into cell A1. Unfortunately the crash report dialog shows not the new generated ID. Also the nightly builds are not up to date, see https://dev-builds.libreoffice.org/daily/master/Win-Arm64@tb77-TDF/ last build was not today or yesterday.
MarRol777: I suppose it's due to the integration of "Frozen" lib (see https://ci.libreoffice.org//job/lo_daily_tb_win_arm64/938/consoleFull#-537852444cd06c086-ffd7-48da-8ce2-d58b9387379c) [build CXX] xmloff/source/style/XMLElementPropertyContext.cxx C:/cygwin/home/tdf/jenkins/dly/s_master/xmloff/source/style/XMLRtlGutterPropertyHandler.cxx(21): fatal error C1083: Cannot open include file: 'frozen/bits/defines.h': No such file or directory make[1]: *** [C:/cygwin/home/tdf/jenkins/dly/s_master/solenv/gbuild/LinkTarget.mk:337: C:/cygwin/home/tdf/jenkins/dly/b_master/workdir_for_build/CxxObject/xmloff/source/style/XMLRtlGutterPropertyHandler.o] Error 2 make[1]: *** Waiting for unfinished jobs.... make: *** [Makefile:303: cross-toolset] Error 2 Tomaz: any idea how to fix this? Jan-Marek/Stephan: any thoughts about the bt provided by MarRol777 bridges/source/cpp_uno/msvc_win32_arm64/cpp2uno.cxx ?
Sorry Tomaz, I had forgotten to put you in cc, could you take a look at my previous comment about failing TB Win ARM?
(In reply to Julien Nabet from comment #7) > Sorry Tomaz, I had forgotten to put you in cc, could you take a look at my > previous comment about failing TB Win ARM? I don't see frozen being unpacked in the console log.. something like: [build UPK] frozen-1.1.1.tar.gz There is no limitations AFAIK why the frozen library shouldn't be used for ARM in the configuration, so I think it's the problem with that TB... Probably a partial build is used for this TB, where it doesn't rebuild everything maybe? Not sure...
(In reply to Tomaz Vajngerl from comment #8) > (In reply to Julien Nabet from comment #7) > > Sorry Tomaz, I had forgotten to put you in cc, could you take a look at my > > previous comment about failing TB Win ARM? > > ... > Probably a partial build is used for this TB, where it doesn't rebuild > everything maybe? Not sure... Searching who owns this TB but https://wiki.documentfoundation.org/Development/Tinderbox#77 ("77" because https://dev-builds.libreoffice.org/daily/master/Win-Arm64@tb77-TDF/) but it references a Linux box
(In reply to Julien Nabet from comment #9) > (In reply to Tomaz Vajngerl from comment #8) > > (In reply to Julien Nabet from comment #7) > > > Sorry Tomaz, I had forgotten to put you in cc, could you take a look at my > > > previous comment about failing TB Win ARM? > > > > ... > > Probably a partial build is used for this TB, where it doesn't rebuild > > everything maybe? Not sure... > > Searching who owns this TB but > https://wiki.documentfoundation.org/Development/Tinderbox#77 ("77" because > https://dev-builds.libreoffice.org/daily/master/Win-Arm64@tb77-TDF/) but it > references a Linux box I sent a message on dev mailing list here: https://lists.freedesktop.org/archives/libreoffice/2023-June/090500.html
Just for the record, I've created a Redmine about the failing daily build for Windows ARM LO. https://redmine.documentfoundation.org/issues/3662
A new daily build is available here: https://dev-builds.libreoffice.org/daily/master/Win-Arm64@tb77-TDF/current/
I tried the new daily build: Version: 24.2.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 26d191e8ee53a38d350c10d5666c6dd8629c8ab2 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded With this Version the problem/bug is solved. No crash any more.
Thank you Julien for troubleshooting and Christian for the patch. Whoever has brought the TB77 back to running again: The dev builds are generated daily again! The TB77 was once launched by Jan-Marek Glogowski, see bug https://bugs.documentfoundation.org/show_bug.cgi?id=137143
Great news! Let’s put this one to WFM then. The only pb is we don’t know what commit fixed it and so for a stable 24.2 version you’ll have to wait for February 2024
Marc: please don't send an email in private (yours had been considered as a spam, hopefully I check the content of spam folder). So you indicated: " after 3 months I installed the newest daily build and now the bug is back again. Version: 24.2.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: adcde78935fb8ca2b93322aa3a558d0b3ccdbfad CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded What should we do now? Open a new bug report? But I don't know how to create a crash report as it was automatically done in Version 7.4.7.2 - because the Development-Version: 24.2.0.0.alpha0+ just crashes and there is no crash report assistant any more." " Several things: 1) 24.2 is a dev version but it's ok if you want to test it before the release. 2) try https://wiki.documentfoundation.org/QA/FirstSteps 3) if you still got a crash, you can retrieve a backtrace by following https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace (it requires a bit of time above all for the first time when you must install some extra components).