<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - FILESAVE Bad Allocation crash (32bit build problem only)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=129121#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - FILESAVE Bad Allocation crash (32bit build problem only)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=129121">bug 129121</a>
from <span class="vcard"><a class="email" href="mailto:baron@caesar.elte.hu" title="Aron Budea <baron@caesar.elte.hu>"> <span class="fn">Aron Budea</span></a>
</span></b>
<pre>(In reply to MarvinWWW from <a href="show_bug.cgi?id=129121#c11">comment #11</a>)
<span class="quote">> If no one can give me any kind of a schedule, then I might have to go buy a
> 64-bit computer in order to get my project back on track...</span >
This is a volunteer-driven project, so there's no particular schedule for
random bugs. If you're going to buy a computer in the end, you should try your
workflow first on a similar machine to make sure it works. Typically when
processing a file takes up a lot of memory, the user experience while working
on the file could be subpar (at least loading/saving). If possible, splitting
up the data into multiple spreadsheets sounds like a good idea.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>