See Bug 82404 Comment #3. 1. enter info into a a few cells in column in Calc spreadsheet 2. select and copy cells 3. click top left corner record selector 4. Fatal error, crash, "bad allocation" LO 5.0.0.3 Windows 7 64-bit, but similar problem 4.2 previously.
Meant to say fatal error after clicking record selector in corner, then ctrl-v paste. Error occurs after paste.
Created attachment 117308 [details] OS message about not enough memory Hi @Doug, thanks for reporting. reproducible with: Win7x64 Version: 4.4.5.0.0+ Build ID: 1ce188a6f3afc69bf2bfeb11d62e287101398884 TinderBox: Win-x86@51-TDF, Branch:libreoffice-4-4, Time: 2015-07-04_00:02:20 Version: 5.0.0.1.0+ (x64) Build ID: df06ddf79cf0b5aca037630504a07dd8b2341a43 TinderBox: Win-x86_64@62-TDF, Branch:libreoffice-5-0, Time: 2015-07-17_18:17:03 In any case remember that doing so, you are copying into: 1024 cols x 1.048.576 rows = 1.073.741.824 cells so is normal not enough memory, but is a bug not being captured the error, what can leads to data loss. Maybe must not be allowed paste on the whole cells.
*** Bug 93180 has been marked as a duplicate of this bug. ***
Intermittently reproduced. First test: Copied date. Select entire SS using box to left of A and above 1. Ctrl-V. Result: small popup briefly saying "bad alloc" or "bad allocation" (unsure), then LO crashes. Second test: Bring it back up, and 3 SSs recovered. Repeat above test, but this time copy number instead of date. No popup. Spinning wheel for several minutes. LO using 22.2 - 23.9% of CPU, and 1,379.8 - 1,426.0 MB of RAM. (Everything together -- Chrome, LO, AV, AMalware, utils, etc. -- using 34% CPU and 68% of RAM) Version: 5.1.1.3 Build ID: 89f508ef3ecebd2cfb8e1def0f0ba9a803b88a6d CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; Locale: en-US (en_US) Windows 10.0.10586 x64 AMD A10-7800 APU 12 GB RAM (physical) + 18.4 GB virtual
OK, after 7-10 minutes of the spinning turquoise wheel, LO Calc flashed the "bad alloc" and crashed (i.e., closed itself).
caolanm->erack: is this now one of the cases caught by the all-spreadsheet-selected new protector ?
*** This bug has been marked as a duplicate of bug 60021 ***