[libreoffice-users] Intentionally crashing LibreOffice when frozen/LibreOffice will not start.

I am working with a data set that keeps causing my LibreOffice to freeze. I
am pretty sure that this is only because it is big. It is a pipe-separated
text from the US Economic Census imported into Calc, about 30 columns and
around a million rows. (The actual data set is bigger, but Calc quits at a
million-odd. The complete file is about 0.8 gig.) I suspect but can not
prove that this is related to file handling somehow, e.g. breaking down
during auto-saving. The first time I saved the data as a Calc file it took
nearly an hour with the "soffice.bin *32" process running at 25 percent of
CPU time and using about 825 meg of memory the entire time. (Not sure why
this is showing up as a 32-bit version).  And when Calc freezes, all the
LibreOffice programs freeze. So I can't just switch to another file and
noodle away while waiting.

So of course, what I really want is a spreadsheet that reads more rows and
doesn't crash. But I assume others are already asking for that, & do not
know how to add anything helpful to that effort. So instead I am asking a
more modest question: What is the best way to crash a frozen LibreOffice if
I want to minimize the data and files lost?

Note that this is the question I started with. Now I have a new and more
urgent question: Why won't LibreOffice start at all? See below.

When Calc froze, I closed it in the usual way with the usual upper-right
close window button. This results in the message:

"The file '$(ARG1)' is corrupt and therefore cannot be opened. LibreOffice
can try to repair the file.

LO can try to repair the file. The corruption could be the result of
document manipulation or of structural document damage due to data
transmission. We recommend that you do not trust the content  of the
repaired document. Execution of macros is disabled for this document. Should
LO repair the file?"

I choose <Yes> 

"Message "The file '$(ARG1)' could not be repaired and therefore cannot be
opened."

The document recovery window said "recovery of your documents was finished"
while the big spreadsheet still said "recovery in process" and a Writer file
said "not recovered yet". Three Writer files said "recovery
successful"Because no LibreOffice process seemed to be using much CPU time,
I assumed that it was again frozen rather than still working (though
"soffice.bin *32" still had 1.14 gig in memory) and hit the "finish" button. 

I got a message, "Fatal Error - Bad Allocation" and nothing was recovered. 

I tried opening Writer, and the document recovery box popped up again, but
with one fewer Writer files listed. This time it started on the spreadsheet,
never finished (though the window again said  "recovery of your documents
was finished") and never got to the remaining files, though I let it run all
night. In the morning I hit finis, and the recovery window disappeared with
nothing taking its place.

I tried to start Writer again. Nothing happened - no error, no window,
nothing. I tried opening a Writer document by clicking on it in Windows
Explorer. Nothing. I tried opening a (different) Calc file. 

Windows Task Manager shows five instances of soffice.bin *32 running, five
instances of soffice.exe * 32, and four instances of swriter.exe *32

I am running LibreOffice 4.2 on Windows 7 64-bit with SP1, on a Dell i5
machine with 24 gig of RAM. I do not recall there being a separate 64-bit
version, but the installer put it in my 64-bit programs directory.

Advice and suggestions most welcome.




--
View this message in context: 
http://nabble.documentfoundation.org/Intentionally-crashing-LibreOffice-when-frozen-LibreOffice-will-not-start-tp4104156.html
Sent from the Users mailing list archive at Nabble.com.

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted