Mailing-List: contact ooo-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-issues@incubator.apache.org
From: bugzilla@apache.org
To: ooo-issues@incubator.apache.org
Subject: [Bug 120338] Deadlock when presenter console is started on first run
 after installation/upgrade
Date: Sat, 21 Jul 2012 09:24:33 +0000
Message-ID: <bug-120338-248469-Qh5vIDkYL7@https.issues.apache.org/ooo/>
In-Reply-To: <bug-120338-248469@https.issues.apache.org/ooo/>
References: <bug-120338-248469@https.issues.apache.org/ooo/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://issues.apache.org/ooo/show_bug.cgi?id=120338

--- Comment #1 from Andre <af@a-w-f.de> ---
The reason for the deadlock is the combination of office and presenter console
running in two separate processes (thus no deadlock on second or later run:
then the extension is run in the same process as the office) and the use of two
threads for the presenter console.
One thread is the "main" thread, the other is called from the timer that is
used to update the display of current and elapsed time.
The presenter console tries to call from both threads back into the office in
the other process.  The calls are routed via cppu, which uses a queue and a
condition to process the calls.  The condition for one call is never set thus
the call is never made.  The office in the first process waits for the call to
be made which it isn't and thus hangs forever.

-- 
You are receiving this mail because:
You are on the CC list for the bug.