Writer document paragraph Heading one - type BladieBla enter enter paragraph Heading two - type BladieBla Insert > Indexes and Tables Tab Entries Select position LS Try to delete that with DEL > Crash Items E# can be removed without trouble (Didn't try the rest).
Created attachment 108912 [details] for convenience, my test document
Error message: ToxLinkProcessor: More calls for CloseLink() than open links exist.
On pc Debian x86-64 with master sources updated yesterday, I don't reproduce this.
Ah well, another 32bits issue :)
On Virtualbox Ubuntu 14.10 with master sources updated 1 week ago, I reproduced the crash. I don't have a bt but retrieved this: C [libvcllo.so+0x22dd06] vcl::Window::ImplCalcOverlapRegionOverlaps(vcl::Region const&, vcl::Region&)+0x40 Cor: could you retrieve a bt with symbols? (since as for me, Virtualbox is quite slow)
Created attachment 109057 [details] bt It seems the bt doesn't come from the original problem but from the call to FatalError so I don't know if it will be helpful.
Now I reproduce this with master sources updated today on pc Debian x86-64 ...
Forgot to add this from console: warn:fwk:14235:1:framework/source/fwi/threadhelp/transactionmanager.cxx:265: TransactionManager...: Owner instance stand in close method. Call was rejected! Chris/Caolan: one for you? (bt includes vcl part)
fixed on master
Michael Stahl committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6b9ab853b6a5fa71c0b6c594ed0e6e6016d13a3b fdo#85872: sw: fix crash in insert index dialog It will be available in 4.4.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.