I have been using a file for my accounting for 5 years. Since a few updates of Libreoffice, it crashes for no apparent reason when opening or after a few seconds. Below is the bug report https://crashreport.libreoffice.org/stats/crash_details/632c98d9-2015-456a-95c2-f0adfecc0d9d
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 196285 [details] Sample document
No reproducible with Version: 24.8.0.3 (X86_64) / LibreOffice Community Build ID: 0bdf1299c94fe897b119f97f3c613e9dca6be583 CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 19042); UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: threaded
Could you please paste the info from Help - about LibreOffice ?
Version: 24.8.0.3 (X86_64) / LibreOffice Community Build ID: 0bdf1299c94fe897b119f97f3c613e9dca6be583 CPU threads: 6; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL threaded
in fact by creating this new "sample" file and emptying it of all the data, this version does not crash... Is it possible that this is linked to the large number of data or formulas?
(In reply to Matthieu Lechevallier from comment #6) > in fact by creating this new "sample" file and emptying it of all the data, > this version does not crash... Is it possible that this is linked to the > large number of data or formulas? Would it be possible to attach the original file ?
it's quite tricky because it contains a lot of financial data of my structure and names of customers, suppliers, employees... But I can try to create a new sample file that I could anonymize
Created attachment 196289 [details] Sample File with data here is an anonymized file. What is strange is that by having made a duplication of the file and opening this copy, calc does not crash... It had done that to me a few weeks ago because the track that had been suggested to me was that I had certainly created this file with an old version of open office and that it posed compatibility problems. So I had started again on a blank version in libreoffice where I had reintegrated all my data and formulas. It worked very well for several days. Then after a few days, it started to crash again...
(In reply to Matthieu Lechevallier from comment #9) > Created attachment 196289 [details] > Sample File with data > > here is an anonymized file. > What is strange is that by having made a duplication of the file and opening > this copy, calc does not crash... > It had done that to me a few weeks ago because the track that had been > suggested to me was that I had certainly created this file with an old > version of open office and that it posed compatibility problems. > So I had started again on a blank version in libreoffice where I had > reintegrated all my data and formulas. > It worked very well for several days. Then after a few days, it started to > crash again... Hi Matthieu, Still not crashing for me. Would it be possible to send me the document privately to my email so I can investigate it further? I promise I won't share it with any third person and I'll delete it as soon as I can get a minimize reproducer.
well now, I can no longer reproduce the bug and calc does not crash for the moment on the original file... Very strange and annoying this bug whose scenario I cannot reproduce... As soon as I fall back into a crash period, I will send you the file.
here it is! I have the impression that there is something that could be linked to the scroll
(In reply to Matthieu Lechevallier from comment #9) > Created attachment 196289 [details] > Sample File with data Regarding the last comment, do you mean you got a crash with this file when scrolling? It did not crash for me when I scrolled around. Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7713d916e06a8388f849a758f928cbcfded6c0ae CPU threads: 2; OS: Windows 11 X86_64 (10.0 build 22621); UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-GB Calc: threaded
I think I finally found the reason for the LibreOffice bug. And it's really crazy! The problem seems to come from cell L4 of the "Compte Radio" tab. In the first version, the width of the column is too small for the result to be displayed. In the second version, I adjusted the width so that the result appears. And in this second version, I can move from left to right using the arrow keys without LibreOffice crashing. The bottom line is, in my opinion, it's the fact that the value in L4 cannot be displayed correctly that causes LibreOffice to suddenly close for me. I don't know if you've managed to reproduce the bug for you. In any case, I hope this observation will help other users who might find themselves facing the same problem.
(In reply to Matthieu Lechevallier from comment #14) > I think I finally found the reason for the LibreOffice bug. And it's really > crazy! > The problem seems to come from cell L4 of the "Compte Radio" tab. > In the first version, the width of the column is too small for the result to > be displayed. > In the second version, I adjusted the width so that the result appears. > And in this second version, I can move from left to right using the arrow > keys without LibreOffice crashing. > The bottom line is, in my opinion, it's the fact that the value in L4 cannot > be displayed correctly that causes LibreOffice to suddenly close for me. > > I don't know if you've managed to reproduce the bug for you. > In any case, I hope this observation will help other users who might find > themselves facing the same problem. According to your description, I think this is related to bug 163091 which is already fixed in LibreOffice 24.2.7 and 24.8.3 *** This bug has been marked as a duplicate of bug 163091 ***