Bug Hunting Session
Bug 66360 - Crash when scrolling up - down Master Document
Summary: Crash when scrolling up - down Master Document
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.4.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-29 11:01 UTC by Bugcruncher
Modified: 2014-09-04 05:30 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bugcruncher 2013-06-29 11:01:10 UTC
Writer will hang after I scrolled up - down between the ends of a complex document with lots of linked slave documents with linked pictures, sections, and so on in it. After some scrolls focus will hang, pictures are flashing, CPU load is at maximum, memory consumption rises and rises. I have to kill soffice.bin by task manager, problem is 100% reproducible for me.

It seems that the problem mainly appears with 
Zoom = adapt height/width 
2 sheets view selected in Status Bar.

I had to fall back to 4.0.3, what does show that problem for me.

This was with a German LibreOffice on WIN XP 7

No way to create a sample document easily, these Master document are embedded into my file system
Comment 1 retired 2013-07-03 12:42:14 UTC
Hi Bugcruncher,

could you please attach an example document showing this behavior? Otherwise it's impossible to reproduce the problem and the exact steps that lead to it, since you say this is reproducible 100% for you.

Also could you try http://www.libreoffice.org/download/pre-releases/ LO 4.1.0.1 and see if you still see the bug with that version?

After providing that additional info please set this bug to UNCONFIRMED.

Thanks :)
Comment 2 Bugcruncher 2013-07-09 11:43:19 UTC
Hi James,
As I said in the report it's not possible to create a sample document, the problem is only reproducible with my complex documents, newly created documents with a more simple structure do not crash.
Comment 3 Bugcruncher 2013-07-11 10:50:27 UTC
I wanted to do some additional tests, but 404 has such a horrible number of crashes in Writer, I uninstalled it again (replaced it with 4.0.3 again) and will not do any further tests with that Version.
Comment 4 Bugcruncher 2013-07-19 16:50:26 UTC
Same Mess with Master documents and with 4.1.0.3 WIN administrative installation
Comment 5 QA Administrators 2014-02-02 02:06:30 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 6 QA Administrators 2014-02-26 19:31:01 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO
Comment 7 Bugcruncher 2014-09-04 05:30:29 UTC
Dear QA Administrators, instead of boring and disguising users with such automated messages you should invest some more time in own attempts to find a way to reproduce the problems users observe.