https://bz.apache.org/ooo/show_bug.cgi?id=125006
dam...@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |CONFIRMED
--- Comment #48 from dam...@apache.org ---
I can reproduce this with the big spreadsheet attached here
(https://bz.apache.org/ooo/attachment.cgi?id=85124), by copying all columns in
the range A to AQ of the "Map" sheet (select the column headers then copy), and
pasting them into a new sheet, and repeating this several times. Each new sheet
they are pasted into increases memory usage by several hundred MB, and when RAM
usage nears 2 GiB, the "bad allocation" messagebox briefly comes up, then
OpenOffice silently exits (probably as even the recovery attempt crashes
separately).
Changing status to CONFIRMED.
Now this spreadsheet is big, but it's not that big. Why is so much memory being
used? Was it being used in older versions of OpenOffice? Maybe not. On bug
124064, the poster gave specific SVN versions which exhibited the problem. One
of the bad versions was 1530680, which is now Git commit
58a710212d90860fe18cdb22f67014b5297207e1, and one of the good versions was
1516435, which is now Git commit 334aff22543c984093b19f3d62460864ecb687cc. It
should be possible to "git bisect" this range of 111 commits, and find the
patch that increased memory usage.
I still do advise using a 64 bit version of OpenOffice until this is fixed,
available on Linux, Mac, and FreeBSD, as it will at least allow you to use all
the memory on your computer and significantly postpone the crash, not limit you
to 2 GiB and early crashes like the 32 bit version on Windows.
--
You are receiving this mail because:
You are the assignee for the issue.
