Issue 6039 - Xcl Imp: Mem usage - 7.4MB Excel file causes 190+MB mem
Summary: Xcl Imp: Mem usage - 7.4MB Excel file causes 190+MB mem
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Windows NT
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2002-06-21 17:53 UTC by jkonecn
Modified: 2013-08-07 15:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

This is an Excel file that is causing the problem. (7.08 MB, application/octet-stream)
2002-07-24 21:25 UTC, jkonecn
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description jkonecn 2002-06-21 17:53:04 UTC
I'm trying to use a 7.4MB excel file and it takes about 2 minutes to load and grinds my PIII550/128MB/WINNT machine to a halt.  It uses
around 90MB of memory when loaded.  I get many "out of memory" error messages while loading.  I'll gladly provide the file but don't know 
where to send it.
Comment 1 jkonecn 2002-07-24 21:25:23 UTC
Created attachment 2325 [details]
This is an Excel file that is causing the problem.
Comment 2 lars 2002-07-25 12:42:02 UTC
Just for information:

I openend it on the System[1] and it took

~15 sec. to OPEN from explorer window as showattachement.xls in OOCalc
                                            (NO OOo app. open already)

~15 sec. to CLOSE by "X" after it was openend as above, specifically 
                         it took that time to remove OOo from display,
                         I could work normally with the not full-sized
                         explorer window after ~1 sec - instead of the
                         desktop there was OOo in the background.

~13 sec. to OPEN from File Open dialogue if OOoCalc is open already
                 (it took the progressbar ~8 sec to get to the right 
                  end, then it stayed there for ~3 sec, then there was
                  ~1 sec no bar but hour-glass, then ~1 sec for "fit-
                  ting" row-height)

~15 sec. to CLOSE by "X" after openend as above; specifically like 
                               the other close procedure two above+

[1] no app. open, Win98 SE, OOo 1.0.0 both ger.lang.ver., 1800XP cpu, 
    384 MB RAM, 101 MB physical free memory reduced, 96 MB swap file 
    usage increased, hd rather not fragmented, hdd. perf (SiSoSan): 
    R/W each, B/S/R ~20,~20, ~5; int ram bw. ~900 MB/s; just tested.
Comment 3 jkonecn 2002-07-25 14:06:03 UTC
I just tried it again.  My CPU utilization was at 100% for about 5 
minutes, memory of soffice was over 98MB.  Finally killed the process.
Prior to opening this file I killed all non-essential processes.

My machine is a P3-550, Windows NT 4 workstation SP6a, 128MB RAM, 
139MB swap file, OOo 1.0.1 english, network install.
Comment 4 jkonecn 2002-07-25 18:32:10 UTC
I just tried again but with the file on a local drive instead of the 
network.  It opens up but memory usage is 89MB.  If I then try to use
the sheet, ie type some values... do a lookup or two, switch between
sheets...  CPU usage jumps to 100% and I have to kill the process.  So 
if anyone tests it again make sure to do some work with the sheet and 
not just open it.  Specifically it seems that using the arrows at the
bottom to scroll from sheet to sheet may be causing the problem.  At 
least that is what I am usually doing when the CPU jumps to 100%.
Comment 5 lars 2002-07-28 15:08:31 UTC
The problem seems to be the memory needed in fact.

As seen in [1] in my post, the total memory needed is ~197 MB.

So this causes long waiting times on lower memory systems if memory 
management (of the app. or the OS) isn't that good.

Total text data is only 1.42 MB; and from what the Navigator 
(standardly F5) shows, there is no additional data; now it will be 
interesting whether it also takes that long (and needs that much 
memory) on other OS (with few memory).

(Changing text entries, switching sheets is no problem on my 384MB 
Comment 6 oc 2002-09-11 12:00:25 UTC
Hi Daniel,
the memory usage seems a little bit high. Please check, if we could 
reduce the memory consumption.
Comment 7 daniel.rentz 2002-10-14 11:27:59 UTC
Will take a look. ->STARTED
Comment 8 daniel.rentz 2003-01-13 16:54:30 UTC
Comment 9 jkonecn 2003-01-28 13:59:15 UTC
Pardon my ignorance... but what does that change in the summary
(Xcl Imp:) mean?
Comment 10 daniel.rentz 2003-01-28 14:29:01 UTC
"excel import", it's just for my convenience to search through my
Comment 11 john.marmion 2003-04-10 18:32:25 UTC
I had a first look at this. Excel stores the Formulae in this document
 in 177,756 records. The Load time and memory usage is a direct result
of that fact. The Load time and memory usage is not a problem of the
Excel Import. Saving and Loading this as a Calc document results in
even some more memory usage.    
Comment 12 frank 2004-05-04 14:49:12 UTC
Due to limited time ressources I re-Target this one to OOo Later