Bug 104094 - Crash after copy and paste larger document
Summary: Crash after copy and paste larger document
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.3.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-21 17:46 UTC by Dieter
Modified: 2016-12-02 12:23 UTC (History)
4 users (show)

See Also:
Crash report or crash signature: ["`anonymous namespace'::lcl_checkClassification(SwDoc *,SwDoc *)"]

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 Dieter 2016-11-21 17:46:08 UTC 
Description:
http://crashreport.libreoffice.org/stats/crash_details/4ecb4246-f563-438c-be38-2842255752d6

Steps to Reproduce:
1. I've copied a document of 34 pages (almost 14.000 words, one picture, 300 comments) (copy all)
2. I've opened a new template
4. Paste => crash

Actual Results:  
Crash

Expected Results:
no crash


Reproducible: Couldn't Reproduce

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
Comment 1 Aron Budea 2016-11-22 02:15:30 UTC 
Bug 100681 returned to haunt? Halloween's supposed to be over.
Old reproduction steps don't work anymore, so this must be something new.
Comment 2 Dieter 2016-11-22 07:54:00 UTC 
Additional information: In difference to Bug 100681 I haven't closed the document after I made the copy.
Comment 3 Buovjaga 2016-11-29 11:22:11 UTC 
Just to verify, does it still crash in a fresh master version: http://dev-builds.libreoffice.org/daily/master/Win-x86@42/current/
Comment 4 Dieter 2016-11-30 21:35:13 UTC 
Everything was fine with version 5.4.0.0.alpha0+
Build ID: 2e0ab512592e2e134faf9612a293fb8fdd0527d0
Comment 5 Buovjaga 2016-12-02 08:01:29 UTC 
Dieter: do you want to keep this report open or should we close? We can always change the status later, if the problem comes back.
Comment 6 Dieter 2016-12-02 12:14:44 UTC 
You can close the report