Bug Hunting Session
Bug 103572 - Writer freezes when saving file to sleeping NAS
Summary: Writer freezes when saving file to sleeping NAS
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.3.0 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Network
  Show dependency treegraph
 
Reported: 2016-10-29 08:45 UTC by peter.comish
Modified: 2019-06-08 03:03 UTC (History)
4 users (show)

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 peter.comish 2016-10-29 08:45:44 UTC
Description:
As per description, if the text document which has been opened from NAS is saved whilst the NAS is not in hibernation mode, then all goes well.  If a file is saved to a sleeping / hibernating NAS (i.e. user uses CTRL+S when NAS is hibernating) then Writer hangs until the NAS wakes and accepts the saved file.  Windows labels the window in which Writer is running as Not Responding and occasionally gives the option of closing the program (writer).  I am experiencing this with a 50 plus page document - I do not know if this would be replicated with a smaller file.  All returns to normal once the NAS has woken, and presumably, the file has been saved.


Steps to Reproduce:
1.  Load a text file from remote storage which is set to power down after 10 minutes.
2.  Wait 11 minutes
3.  Press CTRL + S to save the file to NAS

Actual Results:  
Writer window greyed out by windows and title bar labeled as '- Not Responding'

Expected Results:
Should display a dialogue box or similar as a front end to code waiting for save location availability, should not appear that Writer has crashed to windows.


Reproducible: Always

User Profile Reset: Yes

Additional Info:
I am running version Version: 5.1.5.2
Build ID: 7a864d8825610a8c07cfc3bc01dd4fce6a9447e5
CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; 
Locale: en-GB (en_GB); Calc: group




User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Comment 1 Buovjaga 2016-11-15 12:52:30 UTC
So is it only with Network Attached Storage, or any USB-harddrive that can go to sleep?
Comment 2 Tor Lillqvist 2016-11-15 13:01:20 UTC
Or with *any* kind of storage that is "slow", even if not sleeping at all? Like saving to a SMB or other networked file server over some slow link. Surely we have no special-casing in the code for a "NAS"?
Comment 3 Alex Thurgood 2016-11-15 15:11:17 UTC
(In reply to Tor Lillqvist from comment #2)
> Or with *any* kind of storage that is "slow", even if not sleeping at all?
> Like saving to a SMB or other networked file server over some slow link.
> Surely we have no special-casing in the code for a "NAS"?

Indeed, there are already several reports about crashing/hanging/freezing when network storage is slow, or dies :

bug 87013
bug 41987
bug 97580
bug 81640
Comment 4 Timur 2017-01-30 18:07:06 UTC
Peter, could you find the closest of those that Alex wrote and mark this one as u duplicate? If not, please add to See also.
Comment 5 peter.comish 2017-01-30 18:26:17 UTC
Hi Timur,

Does not appear to be the same issue as the other issues listed appear to be incessant network storage access on Macs, or complete system lock-out on Linux.

This is a windows based issue, that although accessing a file across the network, is not an issue at all unless saving the file, and does not permanently lock out the machine.

What do you mean by add to see also please???
Comment 6 Dieter Praas 2018-09-10 19:45:32 UTC
Peter, unfortunately nothing has happened with this bug report for more than one and a half year. So I'd like to ask, if it is still valid.
Comment 7 Xisco Faulí 2018-10-17 17:28:59 UTC
(In reply to Dieter Praas from comment #6)
> Peter, unfortunately nothing has happened with this bug report for more than
> one and a half year. So I'd like to ask, if it is still valid.

Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 8 QA Administrators 2019-05-08 17:28:00 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2019-05-08 17:58:24 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2019-06-08 03:03:19 UTC
Dear peter.comish,

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