Bug 146148 - Severe lags when working on SMB share on cursor movement and saving file
Summary: Severe lags when working on SMB share on cursor movement and saving file
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.4.1 release
Hardware: x86 (IA32) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: QA:needsComment
Keywords:
Depends on:
Blocks: Network
  Show dependency treegraph
 
Reported: 2021-12-09 14:06 UTC by thdeppner
Modified: 2021-12-26 20:14 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thdeppner 2021-12-09 14:06:24 UTC
Version: 7.2.4.1 / LibreOffice Community
Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9
CPU threads: 4; OS: Mac OS X 10.16; UI render: default; VCL: osx
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

Since about LO 7.0 I experience severe lags on macOS when using LO to work with files that are stored on a network share, mounted via SMB. Lags ("rolling ball") occur when using the cursor-keys to move the cursor for the first time (!) after a document has been opened (note: not first time after LO has been launched, but for each document) and when saving the document to disk. Lags have been experienced with Writer, Calc and Impress (other LO applications have not been tested). Lags seem to be less when "Recent Documents" has been cleared (cp. https://ask.libreoffice.org/t/libreoffice-periodically-accesses-files-in-recent-list-causing-freezes/9240).

Connection speed can be ruled out as a cause, although lags are more severe when accessing files through VPN-tunnel compared to gigabit ethernet, but still occur when connected to ethernet. 

Interestingly, the Windows version of LO (running on a Win7 machine in the same network) does *not* show similar symptoms.
Comment 1 thdeppner 2021-12-09 21:24:19 UTC
Sorry, not a Win7, but a Win10 machine (my mistake).