Bug 118364 - Leaked references warnings from nautilus
Summary: Leaked references warnings from nautilus
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-15 23:22 UTC by Michal Jaegermann
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-04 14:57:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Jaegermann 2004-03-15 23:22:49 UTC
Description of problem:

Running nautilus from explicitely from a command line prompt
results in the following warnings:

(nautilus:3294): Bonobo-CRITICAL **: file bonobo-control-frame.c: line
720 (bonobo_control_frame_set_ui_container): assertion
`frame->priv->activated == FALSE' failed
 
(nautilus:3294): Bonobo-WARNING **: Leaked a total of 2 refs to 2
bonobo object(s)

and after 'nautilus --browser' and a bit of mousing around one
gets:

(nautilus:3679): Bonobo-CRITICAL **: file bonobo-control-frame.c: line
720 (bonobo_control_frame_set_ui_container): assertion
`frame->priv->activated == FALSE' failed
 
--- Hash table keys for warning below:
--> computer:///
--> preferences:///
--> network:///
--> file:///home
--> file:///
 
(nautilus:3679): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash
table still has 5 elements at quit time (keys above)
 
(nautilus:3679): Bonobo-WARNING **: Leaked a total of 8 refs to 8
bonobo object(s)

Version-Release number of selected component (if applicable):
nautilus-2.5.90-1

How reproducible:
withot any trouble :-)

Comment 1 Alexander Larsson 2004-10-04 14:56:58 UTC
Thanks for the bug report. This particular bug has already been reported
to the author of the software, and the Fedora developers don't plan to
work
on it at the moment. You can help out by adding any helpful additional 
information you have to the upstream bug report at:
http://bugzilla.gnome.org/show_bug.cgi?id=80748

If you want to follow what happens to the bug, you can add yourself to
the upstream report.


Note You need to log in before you can comment on or make changes to this bug.