Issue 118798 - Pyuno: dead-lock setting an atrtribute's value
Summary: Pyuno: dead-lock setting an atrtribute's value
Status: CLOSED FIXED
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: current
Hardware: PC Linux, all
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: Ariel Constenla-Haile
QA Contact:
URL:
Keywords:
: 111641 (view as issue list)
Depends on:
Blocks:
 
Reported: 2012-01-16 19:24 UTC by Ariel Constenla-Haile
Modified: 2016-04-09 10:19 UTC (History)
4 users (show)

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

Attachments
Writer document with a macro to reproduce the dead-lock (9.06 KB, application/vnd.oasis.opendocument.text)
2012-01-16 19:24 UTC, Ariel Constenla-Haile 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Ariel Constenla-Haile 2012-01-16 19:24:22 UTC 
Created attachment 77139 [details]
Writer document with a macro to reproduce the dead-lock

How to reproduce it:

org.openoffice.pyuno.MailMessage is implemented in scripting/source/pyprov/mailmerge.py

Setting any of the writable attributes

* ReplyToAddress
* Subject

leads to a dead-lock on Linux.
Comment 1 Ariel Constenla-Haile 2012-01-16 19:29:45 UTC 
Fixed in revision 1232123
Comment 2 hanya 2012-01-16 20:18:09 UTC 
It seems bug 111641 can be closed as duplicate with this.
Comment 3 Ariel Constenla-Haile 2012-01-16 22:11:01 UTC 
(In reply to comment #2)
> It seems bug 111641 can be closed as duplicate with this.

It looks the same issue, I'll take a look with the sample attached there.
Comment 4 Ariel Constenla-Haile 2012-01-25 11:29:29 UTC 
*** Issue 111641 has been marked as a duplicate of this issue. ***
Comment 5 gurfle 2012-01-26 04:31:16 UTC 
At my considerably low-level involvement in bug fixing I am unaware how to figure out when this fix (revision 1232123) will appear in a new release of OOO.  Will it be the very next one?  If not, will someplace (like http://www.openoffice.org/development/releases/3.2.1.html#new) allow one to see?

Thanks, Nick
Comment 6 Ariel Constenla-Haile 2012-01-26 10:07:05 UTC 
(In reply to comment #5)
> At my considerably low-level involvement in bug fixing I am unaware how to
> figure out when this fix (revision 1232123) will appear in a new release of
> OOO.  Will it be the very next one?  If not, will someplace (like
> http://www.openoffice.org/development/releases/3.2.1.html#new) allow one to
> see?

This fix is already integrated in the current Developer Snapshots: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots current revision 1234077
Comment 7 gurfle 2012-01-27 05:08:19 UTC 
So this sounds to me (but am not completely sure) like the fix will be in the next public release, unless some bug uncovered during testing causes it to be undone.

Is that a fair statement about where it goes from here?

Nick
Comment 8 hdu@apache.org 2012-01-27 09:10:13 UTC 
Yes, that is a fair statement.

You can track the latest snapshots at
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots and test your issues on these.
Comment 9 Marcus 2016-04-09 10:19:12 UTC 
fixed in 3.4.x, latest in 4.0.0