Bug 139374 - Crash in: SvTreeList::Remove(SvTreeListEntry const *)
Summary: Crash in: SvTreeList::Remove(SvTreeListEntry const *)
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1 all versions
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-02 18:46 UTC by Joe Killian
Modified: 2021-08-04 03:46 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["SvTreeList::Remove(SvTreeListEntry const *)"]


Attachments
small Writer file that was being edited (19.25 KB, application/vnd.oasis.opendocument.text)
2021-01-02 18:46 UTC, Joe Killian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Killian 2021-01-02 18:46:37 UTC
Created attachment 168635 [details]
small Writer file that was being edited

This bug was filed from the crash reporting server and is br-f9e12d51-c330-4d91-b04d-0455f932070f.
=========================================
Opened Navigator (to see if anything equivalent to Word's Outline View was available for moving sections). Navigator window (undocked) was left open, with Headings highlighted.
  Since no section moving looked available, I selected the second section in the document manually & dragged it before (cursor at left end of) first section & released.
  Writer crashed.
  I note that upon restarting Writer, & recovering docs (there were four open in windows), that 4 copies of the Navigator window opend upon saying finish after recovering.

  I suggest that an equivalent to Word's outline view where text below specified level is collapsed, allowing easy editing of order of headings by selecting & dragging the sections, is an extremely valuable feature that you ought to seriously consider adding.  
  In this case with small headed sections, it would seem easy enough to select a section. But for large documents with multi-page headed sections, it changes a pain-in-the-ass document re-arrangement (reordering sections) to a trivial task. Much to be recommended.

  Thanks, though, for a very nice set of tools.
Joe
Comment 1 Julien Nabet 2021-01-02 21:40:12 UTC
Which Windows version have you got?

LO 6.1.6 is quite old, please give a to LO 7.0.4

You can also try this:
https://wiki.documentfoundation.org/QA/FirstSteps

Finally, please don't mix a bug and a request for enhancement.
Comment 2 Julien Nabet 2021-01-03 10:00:00 UTC
To add a comment, you just have to use the following link:
https://bugs.documentfoundation.org/show_bug.cgi?id=139374#

or this one if you want to attach a file too:
https://bugs.documentfoundation.org/attachment.cgi?bugid=139374&action=enter

So you indicated you got: Win7 Prof 32 bit SP 1
IMHO you should upgrade to Windows 10.
Indeed, according to https://en.wikipedia.org/wiki/Windows_7:
"Windows 7 is eligible for the Extended Security Updates service. This service is available via OEMs, in yearly installments. Security updates are available for the operating system until at most January 10, 2023 only for Professional and Enterprise volume licensed editions"

(you could also try the 64 bits version)

Waiting feedback about 7.0.4
Comment 3 QA Administrators 2021-07-03 04:03:53 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2021-08-04 03:46:15 UTC
Dear Joe Killian,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp