Comment 3 for bug 684361
Revision history for this message
| Mikkel Kamstrup Erlandsen (kamstrup) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I see two possible explanations for this bug:
a) One of the signal handlers on the BamfView "closed" signal frees priv->path, or perhaps more likely:
b) There is exactly one ref on BamfView and there's a signal handler on the "closed" that drops the ref. This would make the priv memory block invalid.
If it's not any of that, then I'm stumped :-)