Bug 41620 - FILESAVE: Drawing Object outside of Page Margins causes CRASH
Summary: FILESAVE: Drawing Object outside of Page Margins causes CRASH
Status: RESOLVED DUPLICATE of bug 47319
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 Beta3
Hardware: Other All
: medium major
Assignee: Cédric Bosdonnat
URL:
Whiteboard: BSA bibisected35 bibisected35older
Keywords: regression
: 47057 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-10-09 09:37 UTC by Rainer Bielefeld Retired
Modified: 2012-03-23 09:57 UTC (History)
8 users (show)

See Also:
Crash report or crash signature:


Attachments
Simplified Test-case (12.09 KB, application/vnd.oasis.opendocument.text)
2012-01-22 09:47 UTC, famo
Details
Screenshot of line in question - for clarification (47.62 KB, image/png)
2012-01-22 09:51 UTC, famo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Bielefeld Retired 2011-10-09 09:37:24 UTC
CRASH when leave document

Steps to reproduce with "LibreOffice 3.4.3  - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:302)]" :
0. Download a.m. sample document
1. Open attachment from "Bug 31748 - [writer] large drawing
   object marked in navigator can not be de-selected
2. Clikc Close-X at top right window corner
3. Click "discard" in message box
   Expected: will close without probem
   Actual: OOo stops responding, WIN error message

Same Problem with Server installation of Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID:  3b32204-7f92fce-2ba0a9f)]" (110903)
Comment 1 Rainer Bielefeld Retired 2011-10-09 09:37:58 UTC
- Reported with Bug Submission Assistant -
Comment 2 Florian Reisinger 2012-01-22 08:09:19 UTC
It crash while changing from read-only to normal

Same OS LibO 3,5rc1
Comment 3 famo 2012-01-22 09:46:33 UTC
I have reduced the mentioned Document as far as possible.

Cause of the crash is a line outside of the page margins, which is normally not possible. Also I cannot reproduce this with a new document (i.e. I cannot move a line outside of the page margins).

So my guess something went wrong on document creation / conversion.
However of course this shouldn't crash LO in any case, but I think the Importance could maybe be reduced.
Comment 4 famo 2012-01-22 09:47:52 UTC
Created attachment 55979 [details]
Simplified Test-case
Comment 5 famo 2012-01-22 09:50:04 UTC
Comment on attachment 55979 [details]
Simplified Test-case

This is the ooolayerfehler.odt File from the other bug, reduced to the line in question.
Comment 6 famo 2012-01-22 09:51:03 UTC
Created attachment 55980 [details]
Screenshot of line in question - for clarification
Comment 7 sasha.libreoffice 2012-02-03 07:42:28 UTC
I can reproduce crash only on Windows, so do not know how extract debuging information about crash
On Fedora 64 bit it not crashes, but present one strangeness: immediately after opening already done 3 or 4 actions.
Comment 8 Rainer Bielefeld Retired 2012-02-03 09:07:12 UTC
Reproducible with famo's sample and with "LibreOffice 3.5.0 RC3 German UI/Locale [Build-ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735] on German WIN7 Home Premium (64bit) 

Reproducible with famo's sample and with "LibreOffice 3.4.5 German UI [Build ID: OOO340m1 (Build:502)]" parallel Server installation on German WIN7 Home Premium (64bit) - hangs stops responding.

Already [Reproducible] with "LibreOffice 3.4.1RC1 - WIN7  Home Premium (64bit) German UI [OOO340m1 (Build:101)]", version details unknown, might also be a daily

No problem with "LibreOffice Portable 3.3.0  - WIN7  Home Premium (64bit) German UI [OOO330m19 (Build:6) tag libreoffice-3.3.0.4]", so REGRESSION
Comment 9 Björn Michaelsen 2012-03-01 08:19:23 UTC
Regression does appear in oldest version of bibisect-3.5.tar.lzma and must be older.
Comment 10 Rainer Bielefeld Retired 2012-03-14 22:28:47 UTC
*** Bug 47057 has been marked as a duplicate of this bug. ***
Comment 11 Michael Stahl (allotropia) 2012-03-21 11:36:09 UTC
cannot reproduce on Linux: master, -3-5 and -3-4 don't crash,
and valgrinding -3-5 doesn't show anything of interest.

could somebody on windows please investigate and at least attach a backtrace?
Comment 12 Petr Mladek 2012-03-23 09:57:47 UTC
It looks like duplicate of #47319 and it seems to be fixed in 3.5.2-rc1.

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