Bug 119769 - Crash in: OutlinerParaObject::OutlinerParaObject(OutlinerParaObject const &)
Summary: Crash in: OutlinerParaObject::OutlinerParaObject(OutlinerParaObject const &)
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.1.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-09 14:36 UTC by lostbits
Modified: 2018-11-16 12:07 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["OutlinerParaObject::OutlinerParaObject(OutlinerParaObject const &)"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lostbits 2018-09-09 14:36:43 UTC
This bug was filed from the crash reporting server and is br-a3a30649-7b8b-403b-89ce-1a5f089b0311.
=========================================
Crash occurred while modifying a table. The approximate sequence is:
1: Create a table (7 rows, 4 columns)
2: Enlarge the table.
4: Merge column 2 & 3.
4: Insert 1 column before column 3 (renumbered columns) - crash

LibreOffice is buggy on Windows (Win10 & Win7). I am getting one crash every 2 days. I have used LibreOffice to create a dump report and recover from the crash. LibreOffice is unable to Open (execute) and I will have to reinstall.

LibreOffice seems to get more buggy with each release. This release is the worst so far.
Comment 1 Roman Kuznetsov 2018-09-09 19:12:40 UTC
don't confirm with steps from description in

Version: 6.1.1.1 (x64)
Build ID: 2718b4a18dfcc6a54ebe5f7b801ee7a47fa81e0c
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
Locale: ru-RU (ru_RU); Calc: CL


but i have questions:

1. OpenGL enabled?
2. What template do you use for presentation?
Comment 2 Xisco Faulí 2018-11-15 14:51:28 UTC
hello lostbits

Do you still reproduce the crash with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?,
Comment 3 lostbits 2018-11-16 00:55:00 UTC
Ahem (also AHo). I can't seem to recreate the error (following my instructions). Consider the issue closed (unless you would prefer to consider the issue 'moribund').

You should change "Bug Hunting Session" to "Bug Hunting Season". Just a thought.

thanks
art
Comment 4 Xisco Faulí 2018-11-16 12:07:45 UTC
Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.