You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2015/06/12 13:14:26 UTC

[Issue 125006] Calc Consistently crashing, usually with "Fatal Error - Bad Allocation"

https://bz.apache.org/ooo/show_bug.cgi?id=125006

John Barrow <jb...@stoneyport.demon.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jb@stoneyport.demon.co.uk

--- Comment #11 from John Barrow <jb...@stoneyport.demon.co.uk> ---
This "Bad Allocation" is affecting my productivity when using AOO4.1.1.  I'm
running a W7 machine with which, in all other respects I have no issues.  The
"BA" message appears in connection with a large spreadsheet (almost 12 Mb
currently) in which I record sales data daily from my business.  The
spreadsheet comprises 21 pages (or sheets?) several of which cross reference
others.  The heart of the spreadsheet are two pages in which the daily sales
records are entered from two distinct sources.  These pages record data
gathered over seven months; sales numbers are entered and their value
calculated from item prices entered as constants at the beginning of the six
months.  These pages each contain approximately 2 000 rows and about 250
columns, so about half a million cells each, and consequently I guess, occupy
most of the almost 12 Mb size of the whole spreadsheet.  

I've been trying to find what's going on through searching the web but no-one
appears to have figured this out yet.  As far as I'm concerned, and others too
from what I read, this fault in AOO is serious.  As I sadi at the beginning it
is affecting my productivity - and that's ironic given the name, "Apache
OpenOffice
The Free and Open Productivity Suite" 

Is "Bad Allocation" an error from within AOO? Or, a Windows error message.  If
the former then presumably(?) somebody in the OO developer community knows what
it takes to generate the error.  It can't just appear on a whim, so to speak. 
So just what is going on.  What's the solution?

-- 
You are receiving this mail because:
You are the assignee for the issue.