Issue 98129 - Printing a selection from Web Layout crashes OOo
Summary: Printing a selection from Web Layout crashes OOo
Status: CLOSED DUPLICATE of issue 101821
Alias: None
Product: Writer
Classification: Application
Component: printing (show other issues)
Version: OOO300m9
Hardware: PC Windows, all
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Oliver Specht
QA Contact: issues@sw
URL:
Keywords: crash, oooqa
: 103115 (view as issue list)
Depends on:
Blocks:
 
Reported: 2009-01-16 00:44 UTC by duane_decker
Modified: 2013-08-07 14:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Large ODT that will exceed 1 "page" in the status bar in web layout. (12.70 KB, application/vnd.oasis.opendocument.text)
2009-01-16 00:48 UTC, duane_decker 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description duane_decker 2009-01-16 00:44:31 UTC 
Printing a selection from Web Layout when past the "first page" crashes OOo.  
This has been 100% reproducible. The ODT file is large, exceeding 65 pages in 
Print Layout. The selection is taken from page 2 of 2 or higher, as viewed in 
the status bar. The same selection prints fine with the document in Print 
Layout. Several error reports have been sent by the OOo error reporting tool 
over the last two months. The latest ID of the error report is rkvxfvc.
Comment 1 duane_decker 2009-01-16 00:48:38 UTC 
Created attachment 59421 [details]
Large ODT that will exceed 1 "page" in the status bar in web layout.
Comment 2 oleghitekschool 2009-01-19 02:57:39 UTC 
The description is not detailed enough, but I managed to reproduce the error as 
described on HP PC, XP with OOo DEV300m37 (Build9371).
Comment 3 eric.savary 2009-03-13 15:56:25 UTC 
As described. Reproduced in 310m3.
Comment 4 marina_hitekschool 2009-04-26 22:45:16 UTC 
Reproduced on OOO310m9, OS windows XP.
Comment 5 Mathias_Bauer 2009-04-28 11:29:51 UTC 
Thanks for reporting this problem to us, it accounts for a lot of crash reports
we received already.

@OS: stack from report

014ae914 5cd67ac4 swmi!ViewShell::CreatePrtDoc+0x103
[o:\ooo300\src.m9\sw\source\core\view\vprint.cxx @ 786]
014aea88 5d169f66 swmi!ViewShell::Prt+0xf9
[o:\ooo300\src.m9\sw\source\core\view\vprint.cxx @ 1006]
014aed3c 5efc3088 swmi!SwView::DoPrint+0xa33
[o:\ooo300\src.m9\sw\source\ui\uiview\viewprt.cxx @ 395]
014af624 5efb5feb sfxmi!SfxViewShell::ExecPrint_Impl+0x17bc
[o:\ooo300\src.m9\sfx2\source\view\viewprn.cxx @ 776]
014af630 5efeeb0a sfxmi!SfxStubSfxViewShellExecPrint_Impl+0xe
[o:\ooo300\src.m9\sfx2\wntmsci12.pro\inc\sfxslots.hxx @ 817]
014af658 5d169521 sfxmi!SfxShell::ExecuteSlot+0xc1
[o:\ooo300\src.m9\sfx2\source\control\shell.cxx @ 964]
014af8a8 5d14e8ea swmi!SwView::ExecutePrint+0x3ca
[o:\ooo300\src.m9\sw\source\ui\uiview\viewprt.cxx @ 555]
014af8b4 5efdc585 swmi!SfxStubSwViewExecutePrint+0xe
[o:\ooo300\src.m9\sw\wntmsci12.pro\inc\swslots.hxx @ 11247]
014af988 5efdf366 sfxmi!SfxDispatcher::Call_Impl+0x3ff
[o:\ooo300\src.m9\sfx2\source\control\dispatch.cxx @ 306]
014afa04 5efdf285 sfxmi!SfxDispatcher::PostMsgHandler+0xdf
[o:\ooo300\src.m9\sfx2\source\control\dispatch.cxx @ 1619]
014afa10 5c7310af sfxmi!SfxDispatcher::LinkStubPostMsgHandler+0xe
[o:\ooo300\src.m9\sfx2\source\control\dispatch.cxx @ 1579]
014afa20 5efff4b9 tlmi!Link::Call+0x11
[o:\ooo300\src.m9\tools\inc\tools\link.hxx @ 142]
014afa30 5efff4d6 sfxmi!SfxHintPoster::DoEvent_Impl+0xe
[o:\ooo300\src.m9\sfx2\source\notify\hintpost.cxx @ 84]
014afa3c 5c7310af sfxmi!SfxHintPoster::LinkStubDoEvent_Impl+0xe
[o:\ooo300\src.m9\sfx2\source\notify\hintpost.cxx @ 87]
014afa4c 5bd79ab9 tlmi!Link::Call+0x11
[o:\ooo300\src.m9\tools\inc\tools\link.hxx @ 142]
014afa54 5bd7abb2 vclmi!ImplHandleUserEvent+0x46
[o:\ooo300\src.m9\vcl\source\window\winproc.cxx @ 1999]
014afab0 5bc5aed1 vclmi!ImplWindowFrameProc+0x2cc
[o:\ooo300\src.m9\vcl\source\window\winproc.cxx @ 2499]
014afac8 5bdbe195 vclmi!SalFrame::CallCallback+0x16
[o:\ooo300\src.m9\vcl\inc\vcl\salframe.hxx @ 286]
014afad8 5bdc3e76 vclmi!ImplHandleUserEvent+0x24
[o:\ooo300\src.m9\vcl\win\source\window\salframe.cxx @ 4503]
014afb18 5bdc4088 vclmi!SalFrameWndProc+0x714
[o:\ooo300\src.m9\vcl\win\source\window\salframe.cxx @ 6047]
014afb64 76aff8d2 vclmi!SalFrameWndProcW+0x30
[o:\ooo300\src.m9\vcl\win\source\window\salframe.cxx @ 6204]
Comment 6 caolanm 2009-07-15 09:46:53 UTC 
*** Issue 103115 has been marked as a duplicate of this issue. ***
Comment 7 Oliver Specht 2009-09-30 09:32:14 UTC 
Target changed to 3.x
Comment 8 Oliver Specht 2009-11-27 13:54:30 UTC 
similar reason as in issue 101821

*** This issue has been marked as a duplicate of 101821 ***
Comment 9 Mechtilde 2009-12-10 21:10:59 UTC 
duplicate -> closed