Bug 120401 - Assertion error: nIndex == iter->pNode->GetIndex() at frmtool.cxx line 1174 on turning off "Track Changes" on a certain doc(x) file.
Summary: Assertion error: nIndex == iter->pNode->GetIndex() at frmtool.cxx line 1174 o...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Crash-Assert
  Show dependency tree / graph
 
Reported: 2018-10-08 06:45 UTC by himajin100000
Modified: 2018-10-08 15:59 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

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 himajin100000 2018-10-08 06:45:21 UTC 
Description:
See steps to reproduce

Steps to Reproduce:
1. Go to tdf#107969 and get the attachment "BEFORE saved - non-bugged file"
2. Load the file. It may take some time. 
3. to turn off "Track Changes" Feature, Go to View->Track Changes from the main menu.

Actual Results:
CRASH with

Version: 6.2.0.0.alpha0+ (x64)
Build ID: e46f8a9a4e3c5b0542c0813b476b449f3af8d607
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-07_23:36:50
Locale: en-US (ja_JP); Calc: CL
-
With my own local build, with dbgutil, 

---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Assertion failed!

Program: C:\build\instdir\program\swlo.dll
File: C:/sources/libo-core/sw/source/core/layout/frmtool.cxx
Line: 1174

Expected Results:
No crash


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Dieter 2018-10-08 07:56:40 UTC 
No crash with

Version: 6.2.0.0.alpha0+ (x64)
Build ID: 48cfa0b00b22f11ade53aec79b2fdddad253e1bd
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-03_02:01:42
Locale: en-US (de_DE); Calc: CL

So perhaps only in the most recent master?
Comment 2 himajin100000 2018-10-08 09:34:22 UTC 
(In reply to Dieter Praas from comment #1)
> No crash with
> 
> Version: 6.2.0.0.alpha0+ (x64)
> Build ID: 48cfa0b00b22f11ade53aec79b2fdddad253e1bd
> CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
> TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-03_02:01:42
> Locale: en-US (de_DE); Calc: CL
> 
> So perhaps only in the most recent master?

crash reproducible with the same version as yours

Version: 6.2.0.0.alpha0+ (x64)
Build ID: 48cfa0b00b22f11ade53aec79b2fdddad253e1bd
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-03_02:01:42
Locale: en-US (ja_JP); Calc: CL
Comment 3 Xisco Faulí 2018-10-08 11:51:34 UTC 
No crash in

Version: 6.2.0.0.alpha0+
Build ID: 4854acc7929ea58632c5d0f7f80a4adc3c62b8cd
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: threaded
Comment 4 Aron Budea 2018-10-08 12:15:47 UTC 
I don't get a crash, either in a Linux dbgutil build, but there are tons of warnings in the console, eg. like this:

warn:sw:8706:8706:sw/source/core/doc/DocumentRedlineManager.cxx:104: redline table corrupted: overlapping redlines

Version: 6.2.0.0.alpha0+
Build ID: 5f5d890c242b8a092804991dba809f6f4287cfb2
CPU threads: 16; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: threaded
Comment 5 himajin100000 2018-10-08 15:59:35 UTC 
profile reset seems to have done the trick. marking RESOLVED WORKSFORME myself