[
https://issues.apache.org/jira/browse/TUSCANY-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476934
]
Caroline Maynard commented on TUSCANY-1147:
-------------------------------------------
That doesn't surprise me too much, there seems to be quite a network of these
dependencies, which will all creep out one by one as we break down the previous
one. Obviously I don't know what you have at 0xb46617b (!) so I can't guess
what you're seeing.
Would you agree with the fix by inspection? If you want to try it, the scenario
is the classic company->departments->employees, where
company->employeeOfTheMonth is a reference to one of the employees. So first
drop the company, while still holding a reference to the employee, then drop
the employee. Bang.
> AccessViolation in DataObjectImpl::clearReferences()
> ----------------------------------------------------
>
> Key: TUSCANY-1147
> URL: https://issues.apache.org/jira/browse/TUSCANY-1147
> Project: Tuscany
> Issue Type: Bug
> Components: C++ SDO
> Affects Versions: Cpp-current
> Environment: Win32, PHP 5.2.1
> Reporter: Caroline Maynard
> Priority: Critical
> Attachments: Tuscany-1147.patch
>
>
> Problem observed when SDO A refers to SDO B. The reference to SDO A is
> dropped. Then the reference to SDO B is dropped. An AccessViolation occurs in
> the SDODataObject destructor, in DataObjectImpl::clearReferences().
> I believe this is because the reference was not properly cleared at the time
> of A's destruction.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
