Bug 91000 - SIDEBAR: Writer crashes when start typing in a blank document after changing tabs
Summary: SIDEBAR: Writer crashes when start typing in a blank document after changing ...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.0.0.0.alpha0+ Master
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace, regression
Depends on:
Blocks:
 
Reported: 2015-05-01 18:06 UTC by Francisco
Modified: 2015-05-27 14:36 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
gdbtrace (8.10 KB, text/x-log)
2015-05-02 05:47 UTC, raal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Francisco 2015-05-01 18:06:00 UTC
Writer crashes when start typing in a new document after changing tabs in sidebar.

Steps:
1) Open Writer
2) Select Styles and Formatting tab
3) Select Track changes tab
4) Select again Styles and Formatting tab
5) Start to write

Result:
Writer crashes

Expect
No crash


Additional comments:
I can reproduce it any time
I have reproduce it with other similar steps as well. 
I have just downloaded LibO 5.0 alpha1. 



Version: 5.0.0.0.alpha1+
Build ID: 010b2d2d9be846fb6b10848204e29e1bc00ef1ea
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-04-29_23:54:29
Locale: es_AR.UTF-8
Comment 1 raal 2015-05-02 05:45:21 UTC
I can confirm with Version: 5.0.0.0.alpha1+
Build ID: 59adad74084e9281887e3f78a225794f37b784d7
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-04-29_12:40:39


Duplicate of bug 90990 ?
Comment 2 raal 2015-05-02 05:47:09 UTC
Created attachment 115257 [details]
gdbtrace

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff3bc5540 in SvTreeListBox::SetUpdateMode(bool) ()
   from /opt/libreofficedev5.0/program/libsvtlo.so
Comment 3 Matthew Francis 2015-05-06 10:26:01 UTC
@raal: I can reproduce this circa April 29th (though not perfectly reliably), but not on current master - how does it look for you now?
Comment 4 tommy27 2015-05-24 07:43:00 UTC
not reproducible under Win8 using 5.1.0.0.alpha1+
Build ID: 83eb114394879cbfd073322a51c47d02553c1fcf
TinderBox: Win-x86@39, Branch:master, Time: 2015-05-22_06:33:51
Locale: en-US (it_IT)

@Francisco 
please retest with a newer LibO 5 build and tell if issue persists or is gone
Comment 5 Francisco 2015-05-24 13:14:13 UTC
(In reply to tommy27 from comment #4)
> not reproducible under Win8 using 5.1.0.0.alpha1+
> Build ID: 83eb114394879cbfd073322a51c47d02553c1fcf
> TinderBox: Win-x86@39, Branch:master, Time: 2015-05-22_06:33:51
> Locale: en-US (it_IT)
> 
> @Francisco 
> please retest with a newer LibO 5 build and tell if issue persists or is gone

@Tommy, sadly, I'll be able to do it on tuesday.
Comment 6 Francisco 2015-05-27 14:33:21 UTC
I confirm that this bug is not present in LibO 5.0b1.

Versión: 5.0.0.0.beta1
Id. de compilación: 0a16c3dda4150008d9be6f24cbd15ac198d116d3
Configuración regional: en-US (es_AR.UTF-8)
Comment 7 tommy27 2015-05-27 14:36:39 UTC
nice to hear that. RESOLVED WORKSFORME