Issue 43628 - [CWS dba24] crash when accessing the properties of a disposed data source
Summary: [CWS dba24] crash when accessing the properties of a disposed data source
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 680m80
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: marc.neumann
QA Contact: issues@dba
Keywords: regression
Depends on:
Reported: 2005-02-27 12:26 UTC by Frank Schönheit
Modified: 2006-05-31 14:29 UTC (History)
1 user (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 Frank Schönheit 2005-02-27 12:26:01 UTC
consider the following Basic macro:
  oDBC = createUnoservice( "" )
  oDS = oDBC.getByName( "Bibliography" )
  oDS.User = "SomeUserName"
  sMessage = "user name: " + oDS.User
  MsgBox sMessage
  sMessage = "user name: " + oDS.User
  MsgBox sMessage

In 680m80, this runs fine, two times displaying "user name: SomeUserName", as
If you run this in CWS dba24, it crashs after the first message box.
Comment 1 Frank Schönheit 2005-02-27 12:27:08 UTC

fs->oj: seems that convert/setFastPropertyValue members do not check for m_pImpl
before accessing it. Please also secure all other methods which need m_pImpl,
and are accessible to external callers.
Comment 2 ocke.janssen 2005-02-28 07:06:33 UTC
Fixed in cws dba24
Comment 3 ocke.janssen 2005-02-28 09:10:40 UTC
PLease verify. Thanks.

re-open issue and try to reassign to
Comment 4 ocke.janssen 2005-02-28 09:10:45 UTC
try to reassign to
Comment 5 ocke.janssen 2005-02-28 09:10:51 UTC
try to reset resolution to FIXED
Comment 6 marc.neumann 2005-03-07 14:48:16 UTC
No crash anymore, but also not really fixed.

wrote follow up issue  43628
Comment 7 christoph.lukasiak 2005-03-16 10:05:03 UTC
Comment 8 christoph.lukasiak 2005-03-16 10:06:55 UTC
clu->msc: as mentioned, your turn
Comment 9 thorsten.ziehm 2005-03-18 10:04:17 UTC
This task should be fixed => set to resolved fixed.
The follow up task is issue 43628
Comment 10 marc.neumann 2005-06-10 11:42:21 UTC
no crash in master -> close