Apache OpenOffice (AOO) Bugzilla – Issue 29789
Crash after previewing a more complicated control scenario
Last modified: 2005-07-25 22:06:49 UTC
1. open a text doc and insert a table control connected to any data source 2. open the control property browser and set property border: without frame 3. switch to page preview -> crash crash report: rzyx2n CLU: does not crash every try, but crash in several situations after previewing a more complicated control scenario
Created attachment 15911 [details] stack of the crash
fs->as: There's a lot of framework- and sfx-stuff on the stack (see attached file), at the moment this looks to me like a framework problem.
AS->CD: MenubarManager is more your area. Please take over. THX.
.
I see a different stack, where the help crashes. Looks like a memory corruption error: <errormail:StackInfo pos="0" ip="0x77F57D85" rel="0x00007D85" ordinal="RtlAllocateHeap+0x000001D7" name="ntdll.dll" path="C:\WINXP\System32\"/> <errormail:StackInfo pos="1" ip="0x7C0010D3" rel="0x000010D3" ordinal="EH_prolog+0x000000D3" name="MSVCR70.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="2" ip="0x7C00107B" rel="0x0000107B" ordinal="EH_prolog+0x0000007B" name="MSVCR70.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="3" ip="0x045FE259" rel="0x0004E259" ordinal="SfxContentHelper::GetActiveHelpString+0x00000129" name="sfx680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="4" ip="0x0470E5B4" rel="0x0015E5B4" ordinal="SfxHelp_Impl::GetHelpText+0x00000098" name="sfx680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="5" ip="0x04710839" rel="0x00160839" ordinal="SfxHelp::GetHelpText+0x00000053" name="sfx680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="6" ip="0x1000B7F9" rel="0x0000B7F9" ordinal="Menu::GetHelpText+0x00000049" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="7" ip="0x046197BD" rel="0x000697BD" ordinal="SfxVirtualMenu::CreateFromSVMenu+0x000007BD" name="sfx680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="8" ip="0x0461A1C8" rel="0x0006A1C8" ordinal="SfxVirtualMenu::SfxVirtualMenu+0x000000C8" name="sfx680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="9" ip="0x04619607" rel="0x00069607" ordinal="SfxVirtualMenu::CreateFromSVMenu+0x00000607" name="sfx680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="10" ip="0x0461A2D1" rel="0x0006A2D1" ordinal="SfxVirtualMenu::SfxVirtualMenu+0x000000C1" name="sfx680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="11" ip="0x0465B275" rel="0x000AB275" ordinal="SfxMenuManager::SfxMenuManager+0x00000075" name="sfx680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="12" ip="0x0465B506" rel="0x000AB506" ordinal="SfxPopupMenuManager::ExecutePopup+0x00000216" name="sfx680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="13" ip="0x046FC7A9" rel="0x0014C7A9" ordinal="SfxDispatcher::ExecutePopup+0x00000151" name="sfx680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="14" ip="0x07D388C9" rel="0x002788C9" ordinal="Ordinal30196+0x0000029E" name="sw680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="15" ip="0x100C3D59" rel="0x000C3D59" ordinal="ImplCallEvent+0x000004D9" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="16" ip="0x100C6883" rel="0x000C6883" ordinal="ImplHandleMouseEvent+0x00000DE3" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="17" ip="0x100C6EC5" rel="0x000C6EC5" ordinal="ImplHandleSalMouseButtonDown+0x00000035" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="18" ip="0x100C6923" rel="0x000C6923" ordinal="ImplWindowFrameProc+0x00000073" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="19" ip="0x1016A43D" rel="0x0016A43D" ordinal="WinSalFrame::GetCurrentModButtons+0x0000036D" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="20" ip="0x1016E24F" rel="0x0016E24F" ordinal="SalFrameWndProc+0x000006FF" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="21" ip="0x1016E81E" rel="0x0016E81E" ordinal="SalFrameWndProcW+0x0000004E" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="22" ip="0x77D43A50" rel="0x00003A50" name="USER32.dll" path="C:\WINXP\system32\"/> <errormail:StackInfo pos="23" ip="0x77D43B1F" rel="0x00003B1F" name="USER32.dll" path="C:\WINXP\system32\"/> <errormail:StackInfo pos="24" ip="0x77D43D79" rel="0x00003D79" ordinal="GetMessageW+0x00000125" name="USER32.dll" path="C:\WINXP\system32\"/> <errormail:StackInfo pos="25" ip="0x77D43DDF" rel="0x00003DDF" ordinal="DispatchMessageW+0x0000000B" name="USER32.dll" path="C:\WINXP\system32\"/> <errormail:StackInfo pos="26" ip="0x101449D9" rel="0x001449D9" ordinal="ImplSalYield+0x00000069" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="27" ip="0x10144ABD" rel="0x00144ABD" ordinal="WinSalInstance::Yield+0x000000BD" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="28" ip="0x1003ADBB" rel="0x0003ADBB" ordinal="Application::Execute+0x0000005B" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="29" ip="0x0040E163" rel="0x0000E163" ordinal="desktop::Desktop::Main+0x00001213" name="soffice.exe" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="30" ip="0x10103CF1" rel="0x00103CF1" ordinal="SVMain+0x000000C1" name="vcl680mi.dll" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="31" ip="0x004316D5" rel="0x000316D5" ordinal="WinMain+0x00000005" name="soffice.exe" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="32" ip="0x00432614" rel="0x00032614" ordinal="WinMainCRTStartup+0x00000191" name="soffice.exe" path="d:\src680m43_49\program\"/> <errormail:StackInfo pos="33" ip="0x77E814C7" rel="0x000214C7" ordinal="GetCurrentDirectoryW+0x00000044" name="kernel32.dll" path="C:\WINXP\system32\"/>
CD: Thanks to AS who found this cause of this issue.
CD: Strange, but now after a number of tests it crashes with a completely different stack in vcl.
CD: Additional code to cache invalidate requests for slots while in update.The assertion is which triggered the lastest crash could be removed. No crash anymore.
CD->CLU: Please verify my bug fix.
verified in cws - no scenario that crashes found anymore
verified
verified in master 680m49
*** Issue 27052 has been marked as a duplicate of this issue. ***