Bug 146059 - LibreOffice Writer 7.2 is slow under Windows 11
Summary: LibreOffice Writer 7.2 is slow under Windows 11
Status: RESOLVED DUPLICATE of bug 145963
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.3.2 release
Hardware: All other
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-05 11:53 UTC by Kees Kriek
Modified: 2021-12-10 09:56 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Calc Guide (Dutch) (10.65 MB, application/vnd.oasis.opendocument.text)
2021-12-05 11:54 UTC, Kees Kriek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kees Kriek 2021-12-05 11:53:06 UTC
Description:
LibreOffice Writer 7.2 is very slow under Windows 11. With Windows 10 there is no problem and also LibreOffice 7.1 under Windows 11 is no problem. When you are working on a large document (see attachment) scrolling to a page down the document and then clicking it is slow. Also selecting a piece of text is very slow. Clicking another paragraph with another paragraph style, takes a while before the new paragraph style is shown in the list.

Steps to Reproduce:
1.Open a large file (see attachment)
2.Scroll down the document
3.Select a piece of text (with the mouse)

Actual Results:
The selection is shown after several seconds

Expected Results:
The selection should be shown immediately s in LO 7.1


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.2.3.2 (x64) / LibreOffice Community
Build ID: d166454616c1632304285822f9c83ce2e660fd92
CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Vulkan; VCL: win
Locale: nl-NL (nl_NL); UI: nl-NL
Calc: threaded

Above says Windows 10 but it is actually and update to Windows 11.
Comment 1 Kees Kriek 2021-12-05 11:54:47 UTC
Created attachment 176709 [details]
Calc Guide (Dutch)
Comment 2 Timur 2021-12-10 09:56:40 UTC
Seems duplicate.

*** This bug has been marked as a duplicate of bug 145963 ***