Issue 47270 - OOo crash with python macro
Summary: OOo crash with python macro
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All Linux, all
: P3 Trivial
Target Milestone: ---
Assignee: joergbudi
QA Contact: issues@api
URL:
Keywords: crash, oooqa
Depends on:
Blocks:
 
Reported: 2005-04-12 16:19 UTC by michele_petrazzo
Modified: 2013-02-24 21:09 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description michele_petrazzo 2005-04-12 16:19:29 UTC
I create a new documente with a button. I assign to this button a python macro
that I have create, and I put to ~/.openoffice.org1.9.91/user/Scripts/python/. 
When I press the button, the first time nothing happen, and at the second press,
OOo crash!  I think that the problems is the dir() python function.

This is my macro:

import uno, unohelper

def try_bug(*args):
    model = XSCRIPTCONTEXT.getDocument()
    print dir(model)
g_exportedScripts = (try_bug,)
Comment 1 stephan.wunderlich 2005-04-12 16:47:51 UTC
sw->jbu: looks like your area
Comment 2 joergbudi 2005-05-02 21:21:18 UTC
Hi,

I reproduced the crash on 680m97, it is probably a problem of the framework, but
I need to debug it to get a sensible stacktrace.

Bye,

Joerg
Comment 3 christianjunker 2005-07-19 00:03:12 UTC
keyword crash.
Comment 4 joergbudi 2005-08-15 19:49:08 UTC
Hi,

should stop guessing, this crash is not related to the scripting framework, but
a bug in pyuno itself. The property __members__ of an bridged uno objects has a
refcount bug, which leads to the crash.

The python builtin dir() function evaluates the __members__ property, so until a
fix is integrated into OOo, using dir() will lead to a crash sooner or later.

BTW, dir() evalutes to nothing currently, this will also be fixed.

Bye,

Joerg
Comment 5 joergbudi 2005-08-15 19:50:33 UTC
set milestone to 2.0.1
Comment 6 christianjunker 2005-10-17 22:35:06 UTC
adding myself to cc. 
cyb->jbu:
If you need any support, let me know.
Comment 7 joergbudi 2005-11-04 19:25:20 UTC
won't get my cws ready for 2.0.1
Comment 8 joergbudi 2005-11-04 19:26:02 UTC
see above
Comment 9 joergbudi 2006-01-12 20:08:32 UTC
fixed on cws_src680_pyunofixes2
Comment 10 joergbudi 2006-03-11 13:59:33 UTC
Hi,

Joerg Skottke (qa representative for pyunofixes2) wants the
submitter to qa their issues themself. You can download the
installationsets either for windows or linux here (
http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/pyunofixes2
). They are based on a OOo2.x-m148 milestone. Can you please
change the state of the issue to verified once you checked, that the bug
is fixed ?

Bye,

Joerg
Comment 11 joerg.skottke 2006-03-19 19:58:47 UTC
Set target
Set verified
Comment 12 ace_dent 2008-05-16 03:28:25 UTC
This Issue is 'Verified' and not updated in 1yr+, so Closing.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew
 
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~