Bug 124831 - Crash in: rtl_uString_newFromStr_WithLength FILEOPEN ODS
Summary: Crash in: rtl_uString_newFromStr_WithLength FILEOPEN ODS
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.2.7.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-18 21:57 UTC by itsGord
Modified: 2019-05-14 07:22 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["rtl_uString_newFromStr_WithLength"]

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description itsGord 2019-04-18 21:57:53 UTC 
This bug was filed from the crash reporting server and is br-1ca55c62-6297-4f13-997f-51a7810e1092.
=========================================

Calc 5.2.7.2 crashed when trying to open a .ods workbook containing 477 small worksheets. Windows Task Manager showed the system was at 80% memory usage, but did not show LibreOffice in the list of running applications.

The problem was repeatable until I rebooted Windows, at which point it stopped happening.
Comment 1 Aron Budea 2019-04-19 01:09:49 UTC 
Version 5.2.7.2 is quite old, please install a current version, 6.1.5 or 6.2.3 and try again. If the crash still occurs sometimes, checking the available free memory would be a good idea.
Comment 2 itsGord 2019-04-24 21:43:53 UTC 
Good point. Will do.
Comment 3 QA Administrators 2019-05-08 21:50:18 UTC Comment hidden (obsolete)
Comment 4 itsGord 2019-05-10 15:01:17 UTC 
Upgraded two weeks ago to 6.1.5.2; have not yet seen a re-occurrence of the problem while running this release.
Comment 5 QA Administrators 2019-05-14 03:03:19 UTC Comment hidden (obsolete)
Comment 6 Xisco Faulí 2019-05-14 07:22:22 UTC 
(In reply to itsGord from comment #4)
> Upgraded two weeks ago to 6.1.5.2; have not yet seen a re-occurrence of the
> problem while running this release.

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.