Issue 112682 - Clipboard copy delay. Containing a workaround which can help solve the issue finally.
Summary: Clipboard copy delay. Containing a workaround which can help solve the issue ...
Status: CLOSED DUPLICATE of issue 49907
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 3.2
Hardware: PC Windows, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@framework
Depends on:
Reported: 2010-06-25 11:11 UTC by rewraziel
Modified: 2010-06-25 11:58 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 rewraziel 2010-06-25 11:11:36 UTC
When you copy text from Writer, IBM Lotus Symphony, and possibly all other OOo
application, there is a delay if a clipboard viewer is running on the system
BEFORE you start any of the mentioned programs.

From the already running clipboard viewing application, it will receive the
message WM_DRAWCLIPBOARD without delay, but will block on GetClipboardData() for
the infamous 5 seconds, and then continue as normal.

This has been an issue for a very long time, as far back as OOo 2.2 or even longer.

Lots of accessibility programs like screen readers use a clipboard viewer to
read copied text. It is very irritating and frustrating for the users of such

There exists a simple workaround, but it's not very obvious.
1. Make sure no clipboard viewing program is running.
2. Open Writer, write some arbitrary text, copy it to clipboard (CTRL+C or
context menu).
3. Now you can run any clipboard viewing software without those nasty delays.

This is, in my opinion, an issue caused by broken clipboard viewer code within
OOo framework. It should, hopefully be easy to fix with these observations.

The workaround has been confirmed by others, at

Why hasn't this been fixed yet? Related issues have been reported almost a
decade ago.
Comment 1 eric.savary 2010-06-25 11:57:56 UTC
Not a P1.
duplicate of issue 49907.
Comment 2 eric.savary 2010-06-25 11:58:26 UTC

*** This issue has been marked as a duplicate of 49907 ***
Comment 3 eric.savary 2010-06-25 11:58:37 UTC