Created attachment 192667 [details] academic paper Hi, The document has Zotero references, and crashes after 2 mins. Everything is up-to-date (OS, libreoffice, Zotero). I tried to copy-paste the document to a fresh document, but it didn't work. Please fix, or give me a workaround so I can continue working. Thanks, Clement.
Hello Clem, Thank for reporting the bug. Unfortunately I didn't managed to reproduce it with the Windows version: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4d381b54d1c598c181b4a21a8bf0db86eb4668d1 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL threaded Let's see if someone can reproduce it in MacOs.
@clem : what do I have to do to make it crash ? I scrolled up and down the document with Version: 7.5.9.2 (AARCH64) / LibreOffice Community Build ID: cdeefe45c17511d326101eed8008ac4092f278a9 CPU threads: 8; OS: Mac OS X 14.2.1; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded and with Version: 7.6.4.1 (AARCH64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Mac OS X 14.2.1; UI render: Skia/Raster; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded and couldn't reproduce a crash on macOS Arm, but I don't see the Zotero extension toolbar, even after updating to Zotero 6.0.32. @clem : when you get a crash, do you see the Apple Crash Reporter propose to send the crash report to Apple ? If you do, before clicking Send, can you copy paste the complete text of the crash report and paste it into a simple text (.txt) file, and then attach it to this bug report (Add an attachment) ?
I managed to install Zotero in Version: 7.6.4.1 (AARCH64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Mac OS X 14.2.1; UI render: Skia/Raster; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded and re-opened the test document, but I still can't reproduce any crashing. Ideally, we'd need the crash trace from the Apple Crash Reporter to possibly help us identify what is triggering the crash.
Created attachment 192730 [details] Apple crash report Here is the apple crash report.
Created attachment 192731 [details] Apple crash report 2 Thanks for trying out. Here is another crash report. It happened while trying to add a Zotero reference, and Zotero also crashed. I'll post the Zotero crash report too. Should I cross-post this issue to the Zotero developers? Thanks, Clément.
Created attachment 192732 [details] Zotero crash report Here is the Zotero crash report associated with the second crash of LibreOffice. Best, Clément.
[Automated Action] NeedInfo-To-Unconfirmed
@clem : thanks for the trace. This can be seen in the trace: "vmRegionInfo" : "0x1 is not in any region. Bytes before following region: 4374478847\n REGION TYPE START - END [ VSIZE] PRT\/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n---> \n __TEXT 104bd4000-104bd8000 [ 16K] r-x\/r-x SM=COW ...MacOS\/soffice", "exception" : {"codes":"0x0000000000000001, 0x0000000000000001","rawCodes":[1,1],"type":"EXC_BAD_ACCESS","signal":"SIGABRT","subtype":"KERN_INVALID_ADDRESS at 0x0000000000000001"}, "termination" : {"flags":0,"code":6,"namespace":"SIGNAL","indicator":"Abort trap: 6","byProc":"soffice","byPid":34646}, "vmregioninfo" : "0x1 is not in any region. Bytes before following region: 4374478847\n REGION TYPE START - END [ VSIZE] PRT\/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n---> \n __TEXT 104bd4000-104bd8000 [ 16K] r-x\/r-x SM=COW ...MacOS\/soffice", "asi" : {"libsystem_c.dylib":["abort() called"]}, "extMods" : {"caller":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"system":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"targeted":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"warnings":0}, "faultingThread" : 0 which is indicative of something attempting to write to a memory address which doesn't exist, cf. KERN_INVALID_ADDRESS message. Which part of LO that might be though, or whether it is Zotero's fault, is unclear to me.
Hi, I asked the Zotero forum (https://forums.zotero.org/discussion/112308/libre-office-zotero-crash#latest) After a few tries, I found out that deleting the bibliography fixed the problem. I could re-insert it afterwards, and it looks stable for now. Many thanks!