https://bugs.documentfoundation.org/show_bug.cgi?id=146497
--- Comment #13 from Colin <that.man.co...@gmail.com> --- @raal @xisco Fauli Would there be any benefit to providing one of your appropriate developers/experts with TeamViewer access to my computer whilst I create the circumstances that invariably precede the crash? That session could be recorded in order that all your colleagues could be provided with an insight into all aspects of that crash. The simple editing of an auto filter array with conditional formatting The resultant corruption to conditional formatting The crash upon exit & save The empty advisory pane for the recovery items The pointless offer to recover "nothing" and start in "safe mode" The auto submission of the crash report The failure of LO to unload itself after the crash The failure of LO to unload itself following a regular load, edit, save & exit The excessive CPU demand attributable to the rogue LO process The excessive Disk Activity attributable to the rogue LO process The requirement for the rogue LO to be manually disabled via Task Manager It is increasingly apparent that the situation is far more significant than just "editing an auto filtered array causes LO to crash - Fix it;)" Also, a new insight - the auto filtered array is adjacent to a second auto filtered array where both have been created as Defined Named Data Ranges. Whilst they both sort independently, where one may be filtered it does indeed impinge upon the visible rows of the second array. Is that a significant revelation? -- You are receiving this mail because: You are the assignee for the bug.
