Issue 127890 - crashes often with "bad allocation" or freezes on autosave
Summary: crashes often with "bad allocation" or freezes on autosave
Status: CLOSED DUPLICATE of issue 125006
Alias: None
Product: Calc
Classification: Application
Component: ui (show other issues)
Version: 4.1.5
Hardware: PC Windows 10
: P5 (lowest) Critical (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-12 14:27 UTC by oopla
Modified: 2018-09-19 23:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description oopla 2018-09-12 14:27:44 UTC
Hi,

calc has become basiaclly unusable since a while, while was on 4.1.4 updated to 4.1.5 (.en) hoping for a fix but to no avail. 

It may crash with 'bad allocation' as soon as I try reference a cell in another sheet, same document.
Also, it may freeze on autosave, status bar showing 'save document' and still grey progress bar. Then only option is to kill the process.

Available RAM seems not the cause. Disks (SSD/SD) look ok on test tools.
Not so obvious cues on where to look for the culprit, happens (also) while editing plain basic table from scratch.

Wonder if culprit may be related to any recent update of the OS. 
Anyway, thought it was due to surges of 'hardware errors' on soffice processes as shown by resources monitor but that happens on any other process as well which appear unaffected, so guess that's not the cause.

OS: Win 10 Pro 1803 27.5.18 build 17134228
HW: Lenovo Yogabook 4GB, SSD HDD

thanx
Comment 1 Keith N. McKenna 2018-09-12 16:02:30 UTC
This appears as if it could be a duplicate of issue 125006. Could you please attach a sample document that displays the problem to be tested.
Comment 2 oopla 2018-09-19 07:50:27 UTC
More cases:

- open CSV some 600 rows x some 10 cols (bank transaction report), added some 5 cols with simple if() and basic math formula, tweaked here and there, rearranged cols. calc was getting slower and slower then trying to save crashed with 'bad allocation'

- new calcsheet, just a bunch of rows x cols, several tweaks, added graph (bar+line), tweaked oarams & layout etc, print-preview, PDF conversion: here the file dialog was incomplete, black icons not all dirs but operation completed and PDF was generated & saved. But then 'save file ...' yielded 'bad allocation'

- new calc, plain simple few cols of numers and few other cols with basic math on such previous cols, tweaks etc, 'save file ...' did not yield the file dialog, tried more times, calc UI washed out all white unresponsive then crashed (firing the issue reporting service of the OS)

maybe related, on restart / recover I get wierd 'unknown / unsupported excel file format' on .xls files that were either 1) native .xls but no such warning on open or 2) .xls saved from calc as 'MS excel 97/XP' format.

I see in resource/performance monitor calc footprint going up quickly as Ii tweak the doc, that's expected to some extent but seems that at some point it break through the roof
Comment 3 oopla 2018-09-19 08:07:12 UTC
(In reply to Keith N. McKenna from comment #1)
> This appears as if it could be a duplicate of issue 125006. Could you please
> attach a sample document that displays the problem to be tested.

sorry, didn't see your msg - yes all that I read in that ticket is pretty much my experience. Also, as last reported, it's not a specific doc issue - initially Ii thought was that doc from Excel with many x-links and file x-refs etc, or the zeveral docs open etc, but then as you see it's s'thing very base basically unrelated to docs type, complexity etc. 

To me, looking at that ticket and my exp, seems that aoocalc (possibly all AOO - e.g. could never use impress with decent reliability) is not really compatible with (at least) windows 7 & up. And I think (also) my exp cues that's an OS-related base issue which may surface or not depending on OS updates

Note I'm running the exe as the installer provided, did not try OS wizard to try & run it in some compat mode
Comment 4 Keith N. McKenna 2018-09-19 23:52:46 UTC
Given the op's statement that issue 125006 accurately describes his problem I am closing this as a duplicate of that issue

*** This issue has been marked as a duplicate of issue 125006 ***