Apache OpenOffice (AOO) Bugzilla – Issue 15445
Print 3D Object in Draw always causes OO crash
Last modified: 2003-09-08 16:52:24 UTC
To simulate: 1. New a Draw document 2. Select the 3D object from the Main Function Bar on the right hand side. 3. Select to insert a cube. 4. Select to insert a cone. 5. Select to print to a valid printer (export to PDF is OK) 6. OO crashes.
This is not reproduceable on a current version. Please have a look at the 1.1 beta2. If the defect still occurs please feel free to reopen thew issue. Thanks for your help.
Closed.
I have mis-selected the version in my previous report. The bug happens in OO1.1beta2. I can reproduce the bug in WinXP platform.
Does this happen on different printers? This seems to be a problem of the printer driver printing graphics. 3D objects are exported as bitmaps for printing. Does the problem happen only in draw or calc, writer, impress, too? Tnaks for your help.
This problem also happens in Impress. I have tried two different printers: HP LaserJet 3300 and HP Injet 700. Printing to both printer in the described procedure will cause OO crashes. I have tried the same procedure in Win2000, it does not cause OO crashs.
In Win2000, the exact behaviour should be: The print job status is in "Buffering" and the Draw/Impress problem is locked in "printing" status. I have to kill the application via Crtl-Alt-Del.
Reproduced easily on OO1.1beta2 on WinXP. (Once I found the !$*!$??#! floating 3d toolbar, that is. Sun's Star Office 6.0 manual was helpful there; page 326, "The Star Office Draw Window", explained that the 3d Objects thingy was the fifth or so thing down on the left side of the window, and you had to long-click on it (!) to bring up the floating menu. Egads.
Reproduced on Linux. Here's a valgrind stack dump. This is identical to issue 15401's stack dump, just a slightly different way to reproduce it. Invalid memory access of size 1 at 0x40352546: (within libvcl644li.so) by 0x4035434E: Printer::GetPreparedMetaFile(GDIMetaFile const&, GDIMetaFile&, long, long) (in libvcl644li.so) by 0x40307629: ImplQPrinter::ImplPrintHdl(Timer*) (in libvcl644li.so) by 0x4030741C: ImplQPrinter::LinkStubImplPrintHdl(void*, void*) (in libvcl644li.so) by 0x402C13DB: Timer::Timeout() (in libvcl644li.so) by 0x402C10DF: ImplTimerCallbackProc() (in libvcl644li.so) by 0x4045ECB1: SalData::Timeout() const (in libvcl644li.so) by 0x4045E71E: SalXLib::CheckTimeout(bool) (in libvcl644li.so) by 0x4045EAE9: SalXLib::Yield(unsigned char) (in libvcl644li.so) by 0x4046786B: SalInstance::Yield(unsigned char) (in libvcl644li.so) by 0x402BB772: Application::Yield() (in libvcl644li.so) by 0x402BB674: Application::Execute() (in libvcl644li.so) by 0x8065846: desktop::Desktop::Main() (in soffice.bin) by 0x402C0486: SVMain() (in libvcl644li.so) by 0x4045D719: main (in libvcl644li.so) by 0x41508913: __libc_start_main (in /lib/libc-2.2.93.so) by 0x805EAA0: (within soffice.bin) Address 0x0 is not stack'd, malloc'd or free'd I think this is the same bug as another one... *** This issue has been marked as a duplicate of 15401 ***