Issue 99932 - 3 performs slowly or hangs when using Windows shares.
Summary: 3 performs slowly or hangs when using Windows shares.
Alias: None
Product: performance
Classification: Code
Component: www (show other issues)
Version: current
Hardware: PC Windows, all
: P2 Trivial with 2 votes (vote)
Target Milestone: not determined
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2009-03-05 20:37 UTC by mojeaix
Modified: 2013-02-07 22:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description mojeaix 2009-03-05 20:37:42 UTC 3 (OOo3) performs slowly or hangs when using Windows shares.

To duplicate these problems, you will need at least two Windows PC's. In my
case, I am using Windows Vista SP1 running OOo3 with a Windows 2008 file server.
Files reside on the Windows 2008 file server over a standard Ethernet network.
These problem have also been observed on peer-to-peer configurations between
Windows XP workstations.

The steps to reproduce these problems are as follows:

1) Create a folder on one Windows PC and enable file sharing for that folder.
Copy/Create into that folder several OOo3 documents.

2) Go to the second Windows PC running OOo3 and use File | Open. Next, browse to
the folder shared on the remote PC. When you try to open a document shared on
the remote PC, there is a very long delay before the file opens. During the
delay OOo3 is unresponsive. Further, when saving an open document to the remote
folder there is also a long delay and OOo3 is unresponsive. Finally, if the
default Templates folder is set to a remote Windows share, then OOo3 hangs when
a user attempts to create a new document from a template.

3) On the Windows PC running OOo3 use File | Open and browse to an OOo document
stored locally. The file file opens instantly.

4) One workaround is to use Windows Explorer to copy the file from the remote
file folder to the local desktop; make changes locally; then save and copy/move
the file back to the remote folder.

5) The local Windows Vista SP1 workstation I am using is a member of a domain.
There is also a Windows 2008 Terminal Server in this environment which is also a
member of the domain. If I log into the Vista PC using a local user account or
domain user account, then the problems described above occur. If I log into the
Terminal Server using a domain user account, then performance is as expected.

These issues appear to be a regression in OOo3 from the performance experienced
in OOo2.
Comment 1 kpalagin 2009-03-06 15:06:36 UTC
Can't reproduce this problem using OO310m3 on WinXP against WS2003 server.

please try latest dev build and see if problem still exists. Also try mapping 
drive to the share.
Comment 2 mojeaix 2009-03-07 01:09:23 UTC
I am seeing the same behavior in OOo-dev 3.1 on the configuration described above. 
When opening an XLS file located on a mapped network drive OOo-dev 3.1 hung with 
the status "calculating". Further, I am seeing sustained CPU utilization of 50% by 
soffice.bin on the client side. 
Comment 3 mojeaix 2009-03-07 02:19:10 UTC
This behavior is also occurring in IBM's Lotus Symphony which is based on
OpenOffice. Interestingly, Microsoft Office 2007 does not exhibit this behavior.
Comment 4 kpalagin 2009-03-07 09:01:12 UTC
what other process is using the rest of CPU time when this is happening?
I still can't repro the problem. Can you repro it in some other environment, 
like at home in two virtual machines?
Comment 5 rpnpif 2010-03-03 07:45:55 UTC
We have the same problem OO 3.2 on a network with domain.

Note this : 
Associating a drive letter with a remote share takes the same long time and same
big latencies for Windows Xp itself when Explorer runs on the path. So I think
that this issue is due to Windows itself or to the network infrastructure. But
perhaps it exists another way to control these path in the Windows API because
Microsoft office has not this issue.

So I suggest that devs should choose another Windows API code to manage remote path.