Bug 151209

Summary: Crash in: mdds::flat_segment_tree<long,bool>::insert_to_pos(boost::intrusive_ptr<mdds::__st::node<mdds::flat_segment_tree<long,bool> > > &,long,long,bool)
Product: LibreOffice Reporter: Julian <jchennales>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: serval2412
Priority: medium    
Version: 7.3.0.3 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: ["mdds::flat_segment_tree<long,bool>::insert_to_pos(boost::intrusive_ptr<mdds::__st::node<mdds::flat_segment_tree<long,bool> > > &,long,long,bool)"] Regression By:
Attachments: sheet where crash occurred

Description Julian 2022-09-28 05:45:50 UTC 
Created attachment 182701 [details]
sheet where crash occurred

This bug was filed from the crash reporting server and is br-27a34fc6-93b3-4bc5-a6ed-f953d5366214.
=========================================

So, sorry if this is not the proper way, I'm just winging it...

The crash happened twice while I was selecting many non-contiguous rows by clicking on the row number with the mouse while holding CTRL

I will attempt to attach the sheet where it happened since it is small and data is essentially meaningless (sticker id's for the world cup album if anyone is interested!)

The sheet itself was simple, 4 columns, about 100+ rows, AutoFilter on the 4 cols.

Hope it helps.
Comment 1 Julien Nabet 2022-09-28 05:53:20 UTC 
Could you give a try to 7.3.6 and if you still reproduce this try with brand new LO 7.4.1?
Comment 2 Julian 2022-09-28 19:43:20 UTC 
I'm sorry. I can't even make it happen again in my current 7.3.0.3
I'll try an stay sharp in case it happens to me again to see if I can replicate.
Comment 3 QA Administrators 2022-09-29 03:56:56 UTC Comment hidden (obsolete)
Comment 4 Julien Nabet 2022-09-29 05:52:25 UTC 
Ok if you still reproduce this, please give a try with https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile.

Let's put this one to WFM for the moment.
Of course, don't hesitate to reopen this tracker if you still reproduce this. In this case, it would be great you provide step by step process to reproduce this.