Bug 98868 - FILESAVE: crash if try save ODT file with track changes compared
Summary: FILESAVE: crash if try save ODT file with track changes compared
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: high critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks: Document-Comparison
  Show dependency treegraph
 
Reported: 2016-03-24 18:39 UTC by Roman Kuznetsov
Modified: 2019-06-04 07:34 UTC (History)
7 users (show)

See Also:
Crash report or crash signature: ["sw::ClientIteratorBase::ClientIteratorBase(SwModify const &)", "GetFrameOfModify(SwRootFrame const *,SwModify const &,SwFrameType,Point const *,SwPosition const *,bool)"]


Attachments
backtrace (41.57 KB, text/x-log)
2017-02-27 16:33 UTC, Xisco Faulí
Details
backtrace with WinDBG from LO 6.3+ (182.88 KB, text/plain)
2019-01-07 17:50 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Kuznetsov 2016-03-24 18:39:25 UTC
Version: 5.1.2.1 (x64)
Build ID: 2603b69c5ec5981bb5f053f8ebfd1f3de00a4c29
CPU Threads: 2; OS Version: Windows 6.1; UI Render: default; 
Locale: ru-RU (ru_RU)

steps for repro:

1. download full getting started guide 4.2 and 5.0 from 
https://wiki.documentfoundation.org/images/0/0f/GS42-GettingStartedLO.odt
and
https://wiki.documentfoundation.org/images/f/f3/GS50-GettingStartedLO.odt
2. open GS Guide 5.0 in LO
3. select menu Edit - Track Changes - Compare Document
4. select GS Guide 4.2 and wait
5. after compare try to save file
6. LO crashes
Comment 1 tagezi 2016-03-24 19:07:58 UTC
I confirm this

OS: Gentoo GNU/Linux 4.1.15-gentoo-r1 x86_64 Intel(R) Core(TM) i5-2450M CPU@2.50GHz
LO 5.1.1.3, building ID: Gentoo official package
Comment 2 Roman Kuznetsov 2016-03-24 19:27:36 UTC
if try compare only one chapter from GS 4.2. and 5.0, then LO not crashes!

i try on chapter 8
Comment 3 steve -_- 2016-03-25 09:59:53 UTC
also confirmed w current master
Version: 5.2.0.0.alpha0+
Build ID: d9c1921c5031e5b372ee9d8db1e00fe7211cdd31
CPU Threads: 4; OS Version: Mac OS X 10.11.4; UI Render: default; 
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2016-03-25_00:52:11
Locale: de-DE (de.UTF-8)
Comment 4 Roman Kuznetsov 2016-03-25 12:22:12 UTC Comment hidden (no-value)
Comment 6 Roman Kuznetsov 2016-09-24 15:02:38 UTC
crash LO is not critical? how long ago is this? Or status "critical" spoils statistic?
Comment 7 Timur 2016-12-20 16:47:31 UTC
https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg 
Critical is for core functions, major for particular docs.

We get crash report with LO 5.2 and similar result with 5.3.

We have some side regression here, LO 5.4.0.0.alpha0+ Build ID: 5903235d57acb13d9d5286d23b443a01aeab9a3c Windows 6.1 TinderBox: Win-x86@39, Branch:master, Time: 2016-12-19_00:12:28 takes loong to opet GS50-GettingStartedLO.odt
"Compare" results with dump. 
I'll report separately.
Comment 8 Buovjaga 2016-12-31 15:42:02 UTC
(In reply to kompilainenn from comment #6)
> crash LO is not critical? how long ago is this? Or status "critical" spoils
> statistic?

No, Timur is reading the flowchart wrong. Reverting severity to critical.
Comment 9 Xisco Faulí 2017-02-27 10:07:56 UTC Comment hidden (obsolete)
Comment 10 Timur 2017-02-27 13:34:14 UTC
Reproduced with master~2017-02-20_05.58.54_LibreOfficeDev_5.4.0.0.alpha0_Win_x86:
Version: 5.4.0.0.alpha0+
Build ID: 76f9e3b417f19c0a16477e0a0e68e2da31d1de6f
CPU Threads: 8; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2017-02-20_05:58:54
Locale: hr-BA (hr_BA); Calc: CL
 and 
LibreOffice_5.3.0.3_Win_x64:
Version: 5.3.0.3 (x64)
Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1
CPU Threads: 8; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; 
Locale: hr-BA (hr_BA); Calc: CL

But crash signature is different now, why?
http://crashreport.libreoffice.org/stats/crash_details/a797917b-5ee0-43ea-8f05-2b773334dde3

Set back as New. Although this may be Bug 98202 dupe.
Xisco, did you test both Lin and Win?
Comment 11 Timur 2017-02-27 13:45:56 UTC
Not Bug 98202 dupe, signatures different. This might be WFM for the first signature, in that case we need to open a new one with the second one.
Comment 12 Xisco Faulí 2017-02-27 15:57:02 UTC Comment hidden (obsolete)
Comment 13 Xisco Faulí 2017-02-27 16:33:11 UTC
Created attachment 131515 [details]
backtrace
Comment 14 Xisco Faulí 2017-02-27 16:37:52 UTC
(In reply to Xisco Faulí from comment #12)
> (In reply to Timur from comment #10)
> > Reproduced with
> > master~2017-02-20_05.58.54_LibreOfficeDev_5.4.0.0.alpha0_Win_x86:
> > Version: 5.4.0.0.alpha0+
> > Build ID: 76f9e3b417f19c0a16477e0a0e68e2da31d1de6f
> > CPU Threads: 8; OS Version: Windows 6.1; UI Render: default; 
> > TinderBox: Win-x86@39, Branch:master, Time: 2017-02-20_05:58:54
> > Locale: hr-BA (hr_BA); Calc: CL
> >  and 
> > LibreOffice_5.3.0.3_Win_x64:
> > Version: 5.3.0.3 (x64)
> > Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1
> > CPU Threads: 8; OS Version: Windows 6.1; UI Render: default; Layout Engine:
> > new; 
> > Locale: hr-BA (hr_BA); Calc: CL
> > 
> > But crash signature is different now, why?
> > http://crashreport.libreoffice.org/stats/crash_details/a797917b-5ee0-43ea-
> > 8f05-2b773334dde3
> > 
> > Set back as New. Although this may be Bug 98202 dupe.
> > Xisco, did you test both Lin and Win?
> 
> Hello Timur,
> You're completely right. It didn't crash for me because I selected 'Accept
> All' in Manage Changes dialog. However, if I select 'Close', LibreOffice
> crashes. The steps are the same as in bug 98202 but as you said, the report
> is different, so let keep both open

backtrace from bug 98202 and from this one look exactly the same though
Comment 15 Julien Nabet 2017-03-19 10:28:20 UTC
Bt are similar + description of bug is similar=>DUP

*** This bug has been marked as a duplicate of bug 98202 ***
Comment 16 Xisco Faulí 2018-11-14 13:41:23 UTC
I get a different crash from bug 98202 when I reproduce this crash -> http://crashreport.libreoffice.org/stats/crash_details/35cbe0bb-668b-46a4-8e0b-13a5342787ee
Comment 17 Timur 2018-11-15 07:56:40 UTC
Let's keep split. Easy to join if resolved.
Comment 18 yellowhank 2018-11-29 09:10:43 UTC
Bug still exists


Version: 6.3.0.0.alpha0+
Build ID: 72e204da9a062282e52d5060e7f633e3b21414ff
CPU threads: 4; OS: Mac OS X 10.10.5; UI render: default; VCL: osx; 
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-11-26_01:27:57
Locale: zh-CN (zh_Hant.UTF-8); UI-Language: en-US
Calc: threaded
Comment 19 Timur 2019-01-07 17:50:28 UTC
Created attachment 148110 [details]
backtrace with WinDBG from LO 6.3+
Comment 20 Telesto 2019-06-04 07:34:19 UTC
FWIW: recently fixed in NeoOffice