https://bz.apache.org/ooo/show_bug.cgi?id=125006
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from [email protected] --- Windows 8.1 TOSHIBA Satellite L55t-A Intel Core i5-4200U CPU 1.60GHz 2.60 GHz RAM 8.00 GB 64-bit OS, 64-based processor AOO410m18(Build:9764) - Rev. 1589052 2014-04-22 11:43:54 (Di, 22 Apr 2014) I'm "camping on" to issue 125006. It's intermittent, but I have tons of experience with it. For months, I have unsuccessfully been trying to replicate this problem. And yet I replicate it all the time in my daily work with AOO Calc. So here goes... To reproduce the problem in AOO: Either start with a virgin Calc spreadsheet or use an old complicated spreadsheet full of formulas and Pivot Tables. Whether working with an old Profile or a recently reset Profile does not seem to matter. Do heads-down data entry or develop new columns with formulas - any mix of activities. Save often. Do other work with your computer such as using a browser to look at your email - or refrain from that. Download from a website, then Insert/Sheet From File. Or don't. Copy text from browser window to cells - or not. Take your time. Don't hold your breath -- but neither can you say "NOT reproducible" after 10 or 20 minutes. Using the above procedure, I get "Open Office 4.1.0 - Fatal Error /!\ bad allocation" several times a week, sometimes up to 4 times a day. I have a folder in Microsoft OneNote that is filling up with screen-shots of what the window looked like when I got "bad allocation", plus notes as to what I was doing at the time, and how the recovery went. Typical notes (some paraphrasing): "Just data entry. Cursor became a plus sign. Tried to save - bad allocation." "Brand new spreadsheet - trying to select an area" with a screen-shot showing a messed-up area on the display, overlaid by the "bad allocation" window. "Pasted from clipboard after not saving from 2:07 to 2:22 - bad allocation" "Heads-down data entry stops accepting input. After a while, input becomes possible again. Immediate Save results in immediate crash (i.e., AOO 'Document Recovery' window)" Granted, the last example is of a failed Save. It did produce 'bad allocation', but Save has been implicated all along as well. By the way, I have had to try LibreOffce. I have not seen 'bad allocation' there yet. -- You are receiving this mail because: You are the assignee for the issue.
