Issue 18931 - unrecoverable error after copying a graphic and then jumping to a page using the "page preview"
Summary: unrecoverable error after copying a graphic and then jumping to a page using ...
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1 RC3
Hardware: PC Linux, all
: P2 Trivial (vote)
Target Milestone: ---
Assignee: h.ilter
QA Contact: issues@sw
URL:
Keywords: crash, oooqa
Depends on:
Blocks:
 
Reported: 2003-09-01 23:33 UTC by firmail
Modified: 2013-08-07 14:43 UTC (History)
1 user (show)

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

Attachments
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 firmail 2003-09-01 23:33:54 UTC 
It's a very useful feature to be able to jump directly to a page in "page
preview" mode by double-clicking on the page to go to.

But when a graphic from a file (.png) is in the writer document and this graphic
is copied into the clipboard (using ctrl+c) and then the "page preview" is
clicked and I try to jump to another page by double-clicking on it in the
preview, then the writer says: "an unrecoverable error has occured" and shuts
down completely.

Sometimes I also get a lot of error messages after each other looking like this:
"Error loading BASIC of document, .../user/basic/Standard/script.xlb: General
Error. Genereral input/output error"
Comment 1 dankegel 2003-09-03 03:16:50 UTC 
Thanks for the good report!

I'm adjusting the priority up and setting a target of 1.1
(the developers may be forced to change the target to 1.1.1 for
practical reasons; hope not).

Reproduced on first try with Red Hat 9 with 1.1.0rc3.
Crash report submitted; I mentioned issue 18931 in the description.

Here's the traceback of the error in v-grind:
Invalid memory access of size 4 
   at 0x48F121D4: (within
/opt/OpenOffice.org1.1.0rc3/program/libsw645li.so)
   by 0x494EDD1F: (within
/opt/OpenOffice.org1.1.0rc3/program/libsw645li.so)
   by 0x496FC4B0: (within
/opt/OpenOffice.org1.1.0rc3/program/libsw645li.so)
   by 0x495E959D: (within
/opt/OpenOffice.org1.1.0rc3/program/libsw645li.so)
   by 0x495E86AF: (within
/opt/OpenOffice.org1.1.0rc3/program/libsw645li.so)
   by 0x46995441: SfxDispatcher::_FillState(SfxSlotServer const&,
SfxItemSet&, SfxSlot const*) (in
/opt/OpenOffice.org1.1.0rc3/program/libsfx645li.so)
   by 0x469A004F: SfxBindings::Update_Impl(SfxStateCache*) (in
/opt/OpenOffice.org1.1.0rc3/program/libsfx645li.so)
   by 0x469A2570: SfxBindings::NextJob_Impl(Timer*) (in
/opt/OpenOffice.org1.1.0rc3/program/libsfx645li.so)
   by 0x469A2431: SfxBindings::LinkStubNextJob_Impl(void*, void*) (in
/opt/OpenOffice.org1.1.0rc3/program/libsfx645li.so)
   by 0x402DF45A: Timer::Timeout() (in
/opt/OpenOffice.org1.1.0rc3/program/libvcl645li.so)
   by 0x402DF1A9: ImplTimerCallbackProc() (in
/opt/OpenOffice.org1.1.0rc3/program/libvcl645li.so)
   by 0x404A3ED9: SalData::Timeout() const (in
/opt/OpenOffice.org1.1.0rc3/program/libvcl645li.so)
   by 0x404A3A27: SalXLib::CheckTimeout(bool) (in
/opt/OpenOffice.org1.1.0rc3/program/libvcl645li.so)
   by 0x404A3D1C: SalXLib::Yield(unsigned char) (in
/opt/OpenOffice.org1.1.0rc3/program/libvcl645li.so)
...
 Address 0xD0 is not stack'd, malloc'd or free'd

And here's a bit of the XML crash report that I submitted;
it agrees totally with v-grind:

<errormail:StackInfo pos="0" ip="0x40bc488e" rel="0x2188e"
name="libsal.so.3" path="/opt/OpenOffice.org1.1.0rc3/program/"/>
<errormail:StackInfo pos="1" ip="0x40bc5061" rel="0x22061"
name="libsal.so.3" path="/opt/OpenOffice.org1.1.0rc3/program/"/>
<errormail:StackInfo pos="2" ip="0x41135568" rel="0x9568"
name="libpthread.so.0" path="/lib/tls/"/>
<errormail:StackInfo pos="3" ip="0x46e71d20" rel="0x727d20"
name="libsw645li.so" path="/opt/OpenOffice.org1.1.0rc3/program/"/>
<errormail:StackInfo pos="4" ip="0x470804b1" rel="0x9364b1"
name="libsw645li.so" path="/opt/OpenOffice.org1.1.0rc3/program/"/>
<errormail:StackInfo pos="5" ip="0x46f6d59e" rel="0x82359e"
name="libsw645li.so" path="/opt/OpenOffice.org1.1.0rc3/program/"/>
<errormail:StackInfo pos="6" ip="0x46f6c6b0" rel="0x8226b0"
name="libsw645li.so" path="/opt/OpenOffice.org1.1.0rc3/program/"/>
<errormail:StackInfo pos="7" ip="0x455ec442" rel="0x292442"
name="libsfx645li.so" path="/opt/OpenOffice.org1.1.0rc3/program/"
ordinal="_ZN13SfxDispatcher10_FillStateERK13SfxSlotServerR10SfxItemSetPK7SfxSlot+0xb4"/>
<errormail:StackInfo pos="8" ip="0x455f7050" rel="0x29d050"
name="libsfx645li.so" path="/opt/OpenOffice.org1.1.0rc3/program/"
ordinal="_ZN11SfxBindings11Update_ImplEP13SfxStateCache+0x100"/>
<errormail:StackInfo pos="9" ip="0x455f9571" rel="0x29f571"
name="libsfx645li.so" path="/opt/OpenOffice.org1.1.0rc3/program/"
ordinal="_ZN11SfxBindings12NextJob_ImplEP5Timer+0x137"/>
Comment 2 Joost Andrae 2003-09-04 17:04:00 UTC 
JA: changed target and priority. This crash occurs in 1.03 as well.
JA: see crash report ID 19165


SBA: To reproduce:
 - Have a Writer doc with a .png graphic (must be in edit mode)
 - Select the .png (Ctrl-C is not needed)
 - File-Page Preview
 - Double-click a page
 - crash
Comment 3 mhousley 2003-09-10 14:23:28 UTC 
I am able to reproduce this in RC4 running on XP as SBA describes 
except that I have to add a final step of double clicking on the 
image before the program crashes.  This issue is also reproducible 
for bmp images.
Comment 4 alex.thurgood 2003-09-25 09:37:24 UTC 
I can confirm that this crash bug is still in RC5 on Linux. I have
sent a crash report to Sun with the report tool.
Comment 5 openoffice 2003-09-29 12:00:21 UTC 
.
Comment 6 openoffice 2003-10-08 10:46:09 UTC 
crash fixed
followup: issue 20828
Comment 7 openoffice 2003-10-10 15:58:25 UTC 
ready for QA
Comment 8 h.ilter 2003-10-13 10:43:42 UTC 
I can still reproduce the crash with the doubleclick.
Comment 9 h.ilter 2003-10-13 12:24:22 UTC 
Verified with wrong CWS. My fault.
Comment 10 h.ilter 2003-10-13 12:24:54 UTC 
Crash part is fixed.
Comment 11 h.ilter 2003-10-13 12:25:30 UTC 
Set to Verified.
Comment 12 h.ilter 2003-10-22 16:03:02 UTC 
Patch is also ok.
Comment 13 h.ilter 2004-01-20 15:22:02 UTC 
Verified with integrated and patch vesion 645m25_8733 = ok