How to reproduce the crash: On a new spreadsheet, click File - Templates - Organize... to open the Template Management window. On the left, double-click MediaWiki, then mediawiki, then Styles to expand it. On the right, expand Untitled 1, then Styles. While holding down the Ctrl, drag-and-drop Heading3 from the left to the right to crash Calc. The same happens without Ctrl. But works on some other styles... OS: Windows XP Professional Version 2002 SP2 HW: Intel Core2 Duo CPU E6750, Asus P5KC motherboard, 4 GB RAM App: LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 Custom install with only English and Hungarian dictionaries/language packs
Tor, I can confirm the crash on win32, it's some stack guard exception being thrown, seemingly from sal (a string class?) - cannot reproduce on linux, valgrind is silent as well - any chance to have a look into this with a debug build?
confirmed on Windows XP sp3 build 2600, jre 1.6.0_24 and LibO 3.3.2 rc2...also attempted on OSX 10.5.8 with same LibO version - calc crashed as well.
*** Bug 36212 has been marked as a duplicate of this bug. ***
Attempting to debug this now with a sfxmi.dll built with debugging, I get an assertion failure in SfxObjectShell::LoadFrom( SfxMedium& /*rMedium*/ ) in sfx2/source/doc/objstor.cxx when expanding the "mediawiki" under "MediaWiki" at the left. No idea if that assertion failure is related to the crash reported here or not. I will ignore it for now.
The crash happens in SfxEnumItemInterface::operator ==(const SfxPoolItem & rItem) in svl/source/items/cenumitm.cxx . Apparently the cast is bogus, or something, so that the code follows a zero vftable pointer, or something like that.
Anyway, this problem seems to happen only for the MediaWiki template things?
I modified Status to Assigned due to facts.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Please test with latest LibO version... Florian
On Windows 3.5.3.2 (installed this morning with a brand new LO profile), I reproduced the crash. On pc Debian x86-64, no crash with master or 3.5 branch (both updated today). However, "heading 3" doesn't appear in Untitled after the drag and drop. I noticed these messages on console with master : a) during the opening "mediawiki" at left (not the folder, the element in it) warn:legacy.osl:5652:1:/home/julien/compile-libreoffice/libo/sfx2/source/doc/objstor.cxx:2807: Base implementation, must not be called in general! b) during the drag and drop with ctrl (trying to put it at the end, we can see a thin black line) warn:svl:5652:1:/home/julien/compile-libreoffice/libo/svl/source/items/itempool.cxx:682: SFxItemPool: wrong item type in Put, with ID/pos 103 warn:svl:5652:1:/home/julien/compile-libreoffice/libo/svl/source/items/cenumitm.cxx:51: unequal type, with ID/pos 103 b1) during the drag and drop without ctrl (with another brand new profile) (trying to put it at the end, we can see a thin black line) warn:svl:5824:1:/home/julien/compile-libreoffice/libo/svl/source/items/itempool.cxx:682: SFxItemPool: wrong item type in Put, with ID/pos 103 warn:svl:5824:1:/home/julien/compile-libreoffice/libo/svl/source/items/cenumitm.cxx:51: unequal type, with ID/pos 103 warn:legacy.tools:5824:1:/home/julien/compile-libreoffice/libo/svtools/source/contnr/treelist.cxx:1621: Entry already in Table
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian