Bug 99603 - Slows down and Crash when multiple files are open or too much of graphics/pics are used
Summary: Slows down and Crash when multiple files are open or too much of graphics/pic...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.1.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: wantBacktrace
Depends on:
Blocks:
 
Reported: 2016-05-01 10:33 UTC by Peeyush
Modified: 2017-05-03 12:01 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peeyush 2016-05-01 10:33:23 UTC
User-Agent:       Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Build Identifier: LibreOffice 5.1.2.2

The components especially LibreCalc and Impress often slows down or crash when I am working on multiple files together simultaneously. 
With Impress, when I am using graphics and many images to build a presentation the editing slows down and while it often gets crashed and worse is sometimes all of sudden while presenting after connecting to overhead projector.

With LibreCalc, while working on multiple spreadsheets usually 3 to 5 at a time. It crashed while working on pivot tables or while saving the files after copy-paste.

Reproducible: Sometimes




[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes


Reset User Profile?No
Comment 1 VLB 2016-05-01 11:02:24 UTC
I have the same experince with calc wi 10 pro 64 bit.
Comment 2 Buovjaga 2016-05-06 12:19:43 UTC
Guys, please try to reproduce while Windbg is attached: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Comment 3 Aron Budea 2017-01-25 14:58:49 UTC
Setting status to NEEDINFO.
Comment 4 Timur 2017-05-03 12:01:42 UTC
Since no response, I'll close as Invalid in order to focus on many already defined bugs. 
As for "crash", since LO 5.2. there's built-in crash report so different errors can be reported separately. 
As for other problems not detectable with crash report, one can use Procdump utility (part of free and useful Sysinternaly Suite) during LO run in order to get a dump (soffice.bin.dmp). 
Procdump can be run manually after LO start or better via simple batch file like attachment 129814 [details], that is used instead of LO icon to start LO.
Dump is then analyzed with https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg.