Bug 126081 - Crash in swlo!SwFlyFrame::getIDocumentDrawModelAccess
Summary: Crash in swlo!SwFlyFrame::getIDocumentDrawModelAccess
Status: RESOLVED DUPLICATE of bug 117215
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks:
 
Reported: 2019-06-25 11:49 UTC by Telesto
Modified: 2019-06-26 08:04 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["SwFlyAtContentFrame::Modify(SfxPoolItem const *,SfxPoolItem const *)"]

Attachments
bt with debug symbols (12.30 KB, text/plain)
2019-06-25 16:43 UTC, Julien Nabet 		Details
View All 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 Telesto 2019-06-25 11:49:04 UTC 
Description:
swlo!SwFlyFrame::getIDocumentDrawModelAccess+0x1997
Probably another variant of bug 117215/ bug 117185 with yet again unique crash signature

Steps to Reproduce:
1. Open attachment 134755 [details]
2. CTRL+A & CTRL+C in header 
3. CTRL+N
4. CTRL+V 2x
5. CTRL+A
6. CTRL+X
7. CTRL+Z (3x)
8. CTRL+Y (3x)


Actual Results:
Crash

Expected Results:
No crash


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.4.0.0.alpha0+ (x86)
Build ID: 60271c4433372097ef5ecc74e522532ebf5af8e0
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-06-19_05:53:39
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: threaded
Comment 1 Julien Nabet 2019-06-25 16:43:39 UTC 
Created attachment 152401 [details]
bt with debug symbols

On pc Debian x86-64 with master sources updated today, I could reproduce this.
Comment 2 Xisco Faulí 2019-06-26 08:04:37 UTC 
Yes, I believe it's the same root cause as bug 117215.
it's not reproducible if before step 2, the blue cycle placed below the header on the right is deleted...

*** This bug has been marked as a duplicate of bug 117215 ***