Issue 74763 - Loop while formatting extended version of doc from issue 60340
Summary: Loop while formatting extended version of doc from issue 60340
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOo 2.2
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-22 08:20 UTC by michael.ruess
Modified: 2013-08-07 14:43 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description michael.ruess 2007-02-22 08:20:22 UTC
Open document (document is confidential, will be provided personally), leave it
open as is (do not start "page formatting manually) -> Loop after a short time
Comment 1 kpalagin 2007-02-24 13:52:26 UTC
Wouldn't this deserve P2/2.3?
Comment 2 michael.ruess 2007-02-26 09:09:27 UTC
P2 - yes, it is a "crash" issue.
Target will be adjusted when resources could be granted to fix this issue.
Comment 3 raindrops 2007-03-13 15:20:04 UTC
Dear developers,

The locked file is available with MRU. I am unable to even open the file, let
alone edit it.

I need a recovered (unlocked) document urgently. Could you send it across
please? That's important for me: The developer has not stopped cursing me for
switching to OOo, as the entire work has come to a standstill!

Earlier I could use MS Word reliably. The only reason to switch to Openoffice
was pdf conversion. But now there is no file, no pdf!

I don't know how long the recovered document will last till it locks up again.
If I convert the file back to MS Word, god only knows how much of the formatting
will be lost!

The only solution seems to use a tweaked OOo. If you have a beta version of OOo
with corrected algorithms, I am ready to take the risk by trying it out. I think
the arrangement would benefit your team also, as they get more feedback.

Please help!
Comment 4 Mathias_Bauer 2007-06-14 20:56:22 UTC
There is a loop in lcl_RecalcRow:

>	sw680mi.dll!lcl_RecalcRow(SwRowFrm & rRow={...}, long nBottom=2147483647) 
Line 1773 + 0x1a bytes	C++
 	sw680mi.dll!lcl_RecalcTable(SwTabFrm & rTab={...}, SwLayoutFrm *
pFirstRow=0x0703121c, SwLayNotify & rNotify={...})  Line 1826	C++
 	sw680mi.dll!SwTabFrm::MakeAll()  Line 2263	C++
 	sw680mi.dll!SwTabFrm::MakeAll()  Line 2671	C++
 	sw680mi.dll!SwTabFrm::MakeAll()  Line 2671	C++
 	sw680mi.dll!SwFrm::PrepareMake()  Line 413	C++
 	sw680mi.dll!SwFrm::Calc()  Line 1060	C++
 	sw680mi.dll!SwFrm::PrepareMake()  Line 409	C++
 	sw680mi.dll!SwFrm::Calc()  Line 1060	C++
 	sw680mi.dll!SwLayAction::FormatLayout(SwLayoutFrm * pLay=0x070310f0, unsigned
char bAddRect=0)  Line 1580	C++
 	sw680mi.dll!SwLayAction::FormatLayoutTab(SwTabFrm * pTab=0x070294e0, unsigned
char bAddRect=0)  Line 2193 + 0x16 bytes	C++
 	sw680mi.dll!SwLayAction::FormatLayout(SwLayoutFrm * pLay=0x0700e554, unsigned
char bAddRect=0)  Line 1710 + 0x13 bytes	C++
 	sw680mi.dll!SwLayAction::FormatLayout(SwLayoutFrm * pLay=0x07008a90, unsigned
char bAddRect=0)  Line 1713 + 0x13 bytes	C++
 	sw680mi.dll!SwLayAction::InternalAction()  Line 911	C++
 	sw680mi.dll!SwLayAction::Action()  Line 660	C++
 	sw680mi.dll!SwLayIdle::SwLayIdle(SwRootFrm * pRt=0x06da56d0, SwViewImp *
pI=0x06e2e428)  Line 2830	C++
 	sw680mi.dll!ViewShell::LayoutIdle()  Line 796	C++
 	sw680mi.dll!SwDoc::DoIdleJobs(Timer * pTimer=0x06b60db4)  Line 1954	C++
 	sw680mi.dll!SwDoc::LinkStubDoIdleJobs(void * pThis=0x06b60cc8, void *
pCaller=0x06b60db4)  Line 1928 + 0xf bytes	C++
 	tl680mi.dll!Link::Call()  + 0x11 bytes	C++
 	vcl680mi.dll!Timer::Timeout()  + 0xa bytes	C++
 	vcl680mi.dll!Timer::ImplTimerCallbackProc()  + 0x75 bytes	C++
 	vcl680mi.dll!SalTimerProc()  + 0x6c bytes	C++
 	user32.dll!77d18709() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for user32.dll]	
 	user32.dll!77d19655() 	
 	user32.dll!77d40494() 	
 	user32.dll!77d1958f() 	
 	user32.dll!77d1919b() 	
 	user32.dll!77d40494() 	
 	user32.dll!77d189e8() 	
 	vcl680mi.dll!ImplDispatchMessage()  + 0x15 bytes	C++
 	vcl680mi.dll!WinSalInstance::AcquireYieldMutex()  + 0x36 bytes	C++
 	vcl680mi.dll!ImplSalYield()  + 0x83 bytes	C++
 	vcl680mi.dll!WinSalInstance::Yield()  + 0x9f bytes	C++
 	vcl680mi.dll!Application::Yield()  + 0x3a bytes	C++
 	vcl680mi.dll!Application::Execute()  + 0x1e bytes	C++
 	soffice.bin!desktop::Desktop::Main()  + 0xf60 bytes	C++
 	vcl680mi.dll!ImplSVMain()  + 0x3c bytes	C++
 	vcl680mi.dll!SVMain()  + 0x1c bytes	C++
 	soffice.bin!_main()  - 0x14 bytes	C++
 	soffice.bin!_WinMain@16()  + 0x15 bytes	C++
 	soffice.bin!__tmainCRTStartup()  Line 578 + 0x1d bytes	C
 	kernel32.dll!7c816d4f() 	
 	kernel32.dll!7c8399f3() 	

In case that gives any hints.
Comment 5 raindrops 2007-06-19 15:21:47 UTC
I used 2.2.1 RC2 and RC3 for a few days; and could actually open and edit the
document. But now I am using dev2.3 m216 now, and I could open the document just
once. Now again it refuses to open.

Each time the Microsoft error report says "hungapp" crashes; with offset 0000.
But even after recovery OOo does not generate the crash report to be sent to Sun.

Please help!
Comment 6 raindrops 2007-06-20 02:45:35 UTC
Confirmed: I went back to 2.2.1 (stable) and it has worked for the last 5
minutes. (Cannot say whether it will work for longer).

So it looks like 2.3 has more unstable design than 2.2.1. The investigator
should check what's the difference in code.
Comment 7 discoleo 2007-08-26 22:47:21 UTC
See also issue 81033 for another (simple) document probably triggering an
infinite loop. The problem there is that OOo document recovery corrupted the
original document, too [Otherwise, why does the document NOT open after the crash?].
Comment 8 frank.meies 2008-01-10 10:39:45 UTC
fme->mru: Does this still loop with a current version (after the intergration of
loopcontrol)?
Comment 9 michael.ruess 2008-01-10 13:11:37 UTC
Can confirm your experience. Does not loop anymore; seems to be fixed by
"loopcontrol".
Comment 10 frank.meies 2008-04-22 12:54:10 UTC
fme->mru: Please close this issue if this is still fixed in a current version.
Comment 11 raindrops 2008-04-22 15:17:38 UTC
Confirmed: 

The latest version of the document mentioned here does not freeze even when left
alone for long durations.
Comment 12 eric.savary 2008-04-22 15:37:32 UTC
fixed
Comment 13 eric.savary 2008-04-22 16:34:50 UTC
closed