Bug 104655 - FILEOPEN ODS: Memory usage for opening file has increased with factor 5
Summary: FILEOPEN ODS: Memory usage for opening file has increased with factor 5
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.3 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:ods
Depends on:
Blocks:
 
Reported: 2016-12-13 21:14 UTC by Telesto
Modified: 2017-06-01 19:19 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2016-12-13 21:14:24 UTC 
Description:
LibO4.0.0.3 needs around 340 MB ram for opening. LibO 5.4.0.0 around 1,4GB tops

Steps to Reproduce:
1. Open attachment 129581 [details] (bug 104639)
2. Compare memory usage Lib4.0 with 5.4

Actual Results:  
Memory usage has increased with factor 5 

Expected Results:
Memory usage should be around 400 MB.


Reproducible: Always

User Profile Reset: No

Additional Info:
Found in
Version: 5.4.0.0.alpha0+
Build ID: ba6b35fc68a01aff72b39eb7809bacb326068668
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-12-13_06:07:39
Locale: nl-NL (nl_NL); Calc: CL

and in
Versie: 4.4.6.3 
Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d
Locale: nl_NL

but not in 
Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89)


User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Comment 1 Xisco Faulí 2016-12-13 23:05:03 UTC 
Confirmed in

-Version: 5.4.0.0.alpha0+
Build ID: 634589b340316ba64b731b4d923c1056be415494
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

Memory usage: 2.7Gbs

-Version: 4.4.0.0.alpha0+
Build ID: d1278ef4849661b9ae0eb7aaf4d74fbf91ccaf11

Memory usage: 2.7Gbs

-Version: 4.3.0.0.alpha0+
Build ID: 6319265b13321d6bfb527c7bd5b910d4dce4f203

Memory usage: 2.7Gbs

but not in

- Version: 4.1.0.0.alpha1+
Build ID: a2c9d4f8bbde97f175bae4df771273a61251f40

Memory usage: 285mbs
Comment 2 Telesto 2016-12-15 11:00:04 UTC 
Repro with a non-debug build. I reach 1,1GB before LibO crashes:
Version: 5.4.0.0.alpha0+
Build ID: b5cc02ee1b582a6f19e23eb2f1deb1392b3974c0
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2016-12-15_02:27:38
Locale: nl-NL (nl_NL); Calc: CL
Comment 3 raal 2017-05-16 18:52:42 UTC 
Hello, could you retest? LO takes ~400 MB with Version: 5.4.0.0.alpha1+
Build ID: 970b431f1a7b6b96c4c9536657ce4fe9d8f5b585
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-05-11_23:27:58
Comment 4 Telesto 2017-05-16 19:12:06 UTC 
Still a repro with:
Version: 5.4.0.0.alpha1+
Build ID: 8c0be54a7da6262dffe04357121814dd22b5d7fe
CPU threads: 4; OS: Windows 6.2; UI render: default; 
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-05-15_01:35:45
Locale: nl-NL (nl_NL); Calc: CL

Going up to 1,4 GB quite often follow by a crash. They issue could be x86 only..
Comment 5 Telesto 2017-06-01 19:19:12 UTC 
No repro with:
Version: 5.5.0.0.alpha0+
Build ID: ec79f3453471ee9b6ae32e71ff16ea99d9b7751c
CPU threads: 4; OS: Windows 6.19; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-05-28_23:21:44
Locale: nl-NL (nl_NL); Calc: CL

nor with:
Versie: 5.4.0.0.beta1 
Build ID: 8672113ead4e403c55e31b1d9a3d1e0f3b299577
CPU-threads: 4; Besturingssysteem:Windows 6.2; UI-render: standaard; 
Locale: nl-NL (nl_NL); Calc: CL

Closing: WFM