Load times in Writer suddenly got very long for specific documents

Sometime in the last couple of weeks documents that I use regularly now have an issue with initial load times.
Tried a number of things to isolate the cause but so far no success. Has anyone got any suggestions as to cause or possible fix?

Issue:

Either double click document to open, or open LO and then open the doc from the recent docs screen.
LO Writer appears to hang and then between 30 - 60 seconds later the document appears on screen OK.

Initiall I thought this was generic but further tests appear to show that this is ONLY with documents that are label sheets created using the File|New|Labels method, i.e. docs that have a lot of frames.

This was fine up to a couple of weeks ago and I’ve never had an issue before on this or previous machine. Load times were pretty instant. It’s not a hardware issue.

Recent changes:

None that I can think of that might be directly relevant, I don’t auto update Windows. When I finally updated during investigation in case it was an LO/OS issue the last update I took was in March this year - when I installed the OS on the machine.
I don’t automatically update LO either and was running 7.1.4 when this started happening. I tried 7.1.5 and 2.0.0 but behaviour is the same.

… but something must have caused this

I have updated Java in the last week.
I take all the Steam client updates (as you have to)
I’ve not installed any new software over this period.
I’ve not updated any driver software.
I’ve not changed anything in the registry in the last month manually.

Additional info about config and from tests

  • List item

I do not load LO at startup. Never have, never needed to. I don’t like programs hanging around in the background - hangover from experience with 8 bit micros and 16K memory I guess! :grin:

  • LO opens fine on it’s own. As instant as it gets.
  • LO opens other documents fine and quickly. Again almost instantly.
  • Writer has this delay with label sheets auto generated. (To be fair I’ve only tested about 7 or 8 of these but they are all copies of each other with content amended.)
  • BUT!!! Once one of these documents is loaded with the long delay another will open as normal i.e. almost instantly.
    ?? Some kind of memory allocation thing going on here?

It makes no difference whether the document is opened from a network drive (normal) or a local SSD, the behaviour is the same. (Although I haven’t timed the two to see if there’s a longer delay on one storage device)

Environment (from Belarc):

Operating System
Windows 8 Professional (x64) (build 9200)
Install Language: English (United Kingdom)
System Locale: English (United Kingdom)

Processor
3.80 gigahertz AMD Ryzen 9 3900X 12-Core
Multi-core (12 total)
Hyper-threaded (24 total)
Board: ASUSTeK COMPUTER INC. PRIME X570-PRO Rev X.0x
Bus Clock: 100 megahertz
BIOS: American Megatrends Inc. 2606 08/13/2020

65440 Megabytes Usable Installed Memory

Drives
ASMT USB 3.0 Destop H SCSI Disk Device (500.11 GB) – drive 1, s/n 00000000000000000000
ASMT USB 3.0 Destop H SCSI Disk Device (4000.78 GB) – drive 2, s/n 00000000000000000000
Samsung SSD 970 EVO Plus 500GB [Hard drive] (500.11 GB) – drive 0, s/n 0025_385B_01B0_3B78.

Thank you for your detailed report.

It could be that you have assigned a printer in the document and it is not turned on at the time you open the document.

If you can please check this and report back here. Thank you.

Indeed. That was the case. For some reason the printer had powered itself down, or one of the family was trying to be helpful… (Normally it’s left on but it’s silent and in low power state so no issue). Switched it back on and Hey presto!
Trouble is at 23:00 when it doesn’t work it was more fun to try to chase down the problem than finish the admin task, at which point of course I would have turned on the printer again!

The worst thing is I can remember working on a service desk 20 years ago and explaining that to users of all Microsoft products! I’d assumed that a more elegant solution would have been found by now. Silly me!

At the very least prompting the user when this happened that the printer assigned to the document can’t be reached would be a reasonable workaround that would remove any user confusion in these circumstances.

Nevertheless, thank you very much!