To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112603
                 Issue #|112603
                 Summary|sax: use rtl::ByteSequence for trivial global objects 
                        |instead of uno::Sequence
               Component|xml
                 Version|DEV300m83
                Platform|All
                     URL|
              OS/Version|Linux
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|PATCH
                Priority|P3
            Subcomponent|code
             Assigned to|mba
             Reported by|cmc





------- Additional comments from [email protected] Tue Jun 22 13:56:43 +0000 
2010 -------
A global uno::Sequence object is a little problematic in that in its dtor
uno::Sequence looks up the types of its contained objects to do correct release
on them. This needs the cppu infrastructure to be working, but that's rather
problematic at shut-down time where there's some nasty life-cycle issues in 
cppu. 

Currently the cppu foo leaks, so this isn't a noticeable issue, but a leaking
cppu causes the threads used by e.g. unopkg to not exit correctly and outlive
process exit and eventual destruction of all used data.

For sax, the whole issue could be side-stepped by using rtl::BytesSequences and
toUnoSequence which is a simple inline cast, so no detrimental performance issue
should exist.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to