LO Document has become unusable .....?

Hi All,

Hoping someone can help. I have hit a problem with LibreOffice.

I sent a working version of my LO document (.ods format) to a colleague who added some raw data to the sheet. I got it back and was working on it all day yesterday, saving interim copies as I went along throughout the day.

The sheet was getting slower and slower as time went on (it is quite a large and complicated spreadsheet) until I suddenly got the “pizza wheel of death” (Apple Mac). I had to force quit, and ever since then, every copy I made thoughout the day, takes forever to load, and once it does, anything I do, including simply trying to navigate around the sheet, effectively freezes LibreOffice.

I’ve tried doing a “Save As…” immediately upon open, but that just never completes, and as best as I can tell, it’s “crashed” LO. I’ve waited for 15 minutes sometimes hoping it will clear, but I always end up having to force quit.

Smaller, simpler, totally unrelated documents seem to work fine. Even the original I sent my colleague, and the first working version he sent me back, appear to be functioning as expected.

All other “Save As…” copies exhibit the same problem, including the very earliest.

Anyone got any ideas?

Thanks in advance.

CT

I am not sure that I could add anything, I don’t have a clear understanding of LET.
If your colleague uses Excel then it could be a result of internal conversion to and from .ods
Sometimes copying everything to a new spreadsheet removes some corruption but for complex sheets it might be tricky.
Have a look in Navigator for unexpected items.
It might be quicker to go back to the original emailed spreadsheet and add the raw data by pasting as unformatted text then rebuilding today’s work.

Hey Earnest,

Thanks for the reply.

I’m not sure that what I’m experiencing is directly related to LET, as I’ve had LET implemented in a couple of key areas of the sheet for a few days now, but I wouldn’t put it past that being related to the issue somehow.

He’s definitely on the same build of LO as me, well he fresh installed about a week ago, so there is some justified assumption in that statement.

Yeah, that’s what I’m trying to avoid. Could be a major headache.

I fear you may be right. A whole day’s work down the chute. A hard pill to swallow. Damn it!!

The daft thing is, I can get the sheet to open, but as soon as I try to “Save As…”, it’s goodnight Irene, so it’s something to do with what I added yesterday infecting the system, even across several iterations of earlier copies that were working fine as I went along.

It’s like a corruption of a user pref or some such?? I dunno. Frustrating. I wonder what timezone @mikekaganski is in??

Thanks for the reply.

Regards.

CT

Please test in safe mode, Menu/Help/Restart in Safe Mode

Thanks Mariosv,

I’m trying that as we speak. Not sure which settings to “check” in the safe mode restart box. Experimenting with that now.

Cheers.

CT

Continue in Safe Mode. Is the file still crashing? If not the it is User Profile, if it still crashes then it is the file, probably.

Thanks Earnest,

So, I managed to get a “Save As…” to go through on a recent version of the file. Not sure what settings made it work in the Safe mode. I tried it with several different settings in a row, so maybe there’s a cumulative effect of rewriting certain prefs or some such.

The file is loading under normal restart now, but feels very creaky. Saves take forever, but they do work eventually for now. :angry:

I’m wondering if there’s some effect of having “round trip’d” it to my colleague and back?? Is that possible do you think?

One strange thing I noticed was, I’d been struggling with getting some conditional formatting to “take” on some data columns using “Formula is…”. I was busy with a million other chores in the sheet, so I knew I’d come back and unpick that problem later. The very first time I opened his returned file, I saw one of the columns had my conditional formatting suddenly show up, but it subsequently stopped working again. Given my current problems, that’s just one of those things that makes you go “Hmmmmm…”

Thanks again for the feedback/help.

Cheers.

CT

As it is working now: can you post an anonymized copy here?

OpenCL and Skia/Vulkan are turned off, see First steps to take before submitting a bug - The Document Foundation Wiki

It still sounds like an issue with the file but you could click Tools > Options > LibreOffice > View and tick the box Force Skia software rendering, allow LibreOffice to restart and see if there is an improvement in performance.

Guys,

I need to run some chores for a couple of hours. I will be back to this when I get home again.

MS777. Are you a formularisation expert by chance? Know anything about LET functions??

CT

… LET functions are quite new for me, too. But I have ~20 y experience in finding problems in OO documents
Before you submit a bug, it is always good to exclude that the bug is connected to some specific properties of your installation …

Yesterday, while testing ‘=LET()’, something inexplicable happened to me when I tried to enter something. LO automatically converted this function into a Matrix{=…} function block, which has since been missing ‘LET()’.
So far I haven’t been able to get a ‘=LET()’ function to work.

Did you save the intermediate copies as new files: “safe as…”? Then find the most recent file that works well. If you only have one intermediate file that you’ve always overwritten, then you’ve made a typical user error. If you’re extremely lucky, you might find the cell with the programming error. Or you can go through the program code line by line, counting the parentheses, and spot a typo or missing part of a line. There are programs in C++ that let you test your code for errors. I doubt LO programmers have developed anything similar. Therefore, I recommend you will copy the contents of the table and paste it into the new blanc table as plain (unformatted) text to at least save the sensitive data. A very nice job for rainy holidays :woozy_face: