Bug 134327

Summary: A document window consumes 15mb (even when minimized)
Product: LibreOffice Reporter: Telesto <telesto>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: l.lunak
Priority: medium Keywords: needsDevEval
Version: Inherited From OOo   
Hardware: All   
OS: All   
See Also: https://bugs.documentfoundation.org/show_bug.cgi?id=118536
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Screencast

Description Telesto 2020-06-26 19:09:44 UTC
Description:
A document window consumes 15mb (even when minimized)

Steps to Reproduce:
1. Open 4 Writer Windows
2. Downsize them to small Window
3. Maximize them

Actual Results:
+/- 15 MB needed painting a Writer Window. Every new Window will add 15 MB (for my 23 inch 96 DPI screen). Doesn't matter if the Window is visible or not. Resizing at the corner causes decrease in memory usage

So 10 windows = 150 MB

Expected Results:
Not sure if an optimization is possible.. behavior is there since 3.3.0


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: 006c65bbd472cb1d7d44e095714e28190b76be0d
CPU-threads: 4; Besturingssysteem: Windows 6.3 Build 9600; UI-render: standaard; VCL: win
Locale: nl-NL (nl_NL); GI: nl-NL
Calc: CL

already in
3.3.0
Comment 1 Telesto 2020-06-26 19:10:38 UTC
Created attachment 162435 [details]
Screencast
Comment 2 Telesto 2020-06-26 19:16:48 UTC
Calc actually 20 MB
Comment 3 Telesto 2020-06-30 19:32:40 UTC
@Luboš
An opinion need from someone with far more knowledge about backends and VCL. Is this actually needed, or something inherited from the old days.. It's a bit of linear approach, not very intelligent. Not that has to be.. It works.. but needs this really to be managed this way? Can Skia do better :-).

If not, please close
Comment 4 Luboš Luňák 2020-07-02 08:24:52 UTC
At 1920x1080 the backing store for such a window is ~8MiB. Plus doubled because of bug #134342. And additional 15MiB per a window is unlikely to be a realistic problem nowadays.

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