After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 80748 - nautilus leaks Bonobo objects
nautilus leaks Bonobo objects
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
0.x.x [obsolete]
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 84761 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-05-03 23:17 UTC by Diego González
Modified: 2007-06-10 19:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Diego González 2002-05-03 23:17:58 UTC
if i start nautilus, it open a window showing my home directory, if i
inmediately (without doing anything within nautilus) remove nautilus from
the session using the session properties dialog, nautilus quits showing
this on the console:

(nautilus:19991): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash
table still has 3 elements at quit time (keys above)

--- Hash table keys for warning below:
--> file:///home/diego
--> file:///home/diego/.gnome2/nautilus-scripts
--> file:///home

(nautilus:19991): Eel-WARNING **: "nautilus-directory.c: directories" hash
table still has 3 elements at quit time (keys above)

(nautilus:19991): Bonobo-WARNING **: Leaked a total of 10 refs to 10 bonobo
object(s)

** (nautilus:19991): WARNING **: CORBA_ORB_destroy: ORB still has 2 refs.

** (nautilus:19991): WARNING **: ORB: a total of 45 refs to 26 ORB objects
were
Comment 1 Luis Villa 2002-05-20 16:55:45 UTC
Michael:
1) is this a serious problem at all?
2) if so, think you can fix it?

I don't have enough clue about what bonobo/orbit do after shutdown to
judge the severity.
Comment 2 Michael Meeks 2002-05-21 07:19:49 UTC
not very serious at all, typically each object leak is a very small
amount of memory. They should be fixed sometime though.
Comment 3 Luis Villa 2002-05-21 19:20:52 UTC
Marking down a bit, then.
Comment 4 Kjartan Maraas 2003-10-28 07:59:27 UTC
This is from 2.4.x:

(nautilus:4829): Eel-WARNING **: "nautilus-directory.c: directories"
hash table still has 11 elements at quit time (keys above)
 
(nautilus:4829): Bonobo-WARNING **: Leaked a total of 53 refs to 48
bonobo objec t(s)

So it's still there.
Comment 5 Kjartan Maraas 2003-10-28 08:04:19 UTC
*** Bug 84761 has been marked as a duplicate of this bug. ***
Comment 6 Kjartan Maraas 2005-01-05 13:38:12 UTC
And 2.8.x says:

(nautilus:12441): Eel-CRITICAL **: file eel-preferences.c: line 872
(preferences_entry_remove_callback): assertion `entry->callback_list != NULL' failed

** (nautilus:12441): WARNING **: destroyed file still being monitored

** (nautilus:12441): WARNING **: destroyed file still being monitored

** (nautilus:12441): WARNING **: destroyed file still being monitored

** (nautilus:12441): WARNING **: destroyed file still being monitored

--- Hash table keys for warning below:
--> file:///home/kmaraas/Desktop

(nautilus:12441): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table
still has 1 element at quit time (keys above)

--- Hash table keys for warning below:
--> file:///home/kmaraas/Desktop

(nautilus:12441): Eel-WARNING **: "nautilus-directory.c: directories" hash table
still has 1 element at quit time (keys above)

(nautilus:12441): Bonobo-WARNING **: Leaked a total of 3 refs to 3 bonobo object(s)
[kmaraas@localhost bin]$
Comment 7 Jaap A. Haitsma 2005-03-03 23:14:38 UTC
Don't get the bonobo leaks anymore in the current CVS builds. A lot of bonobo
stuff was removed during 2.9.  I guess this bug can be closed


I now get the following when I remove nautilus from my session

(nautilus:6049): Eel-CRITICAL **: preferences_entry_remove_callback: assertion
`entry->callback_list != NULL' failed

** (nautilus:6049): WARNING **: destroyed file still being monitored

** (nautilus:6049): WARNING **: destroyed file still being monitored

** (nautilus:6049): WARNING **: destroyed file still being monitored

** (nautilus:6049): WARNING **: destroyed file still being monitored


BTW Kjartan can you tell me how I can the assertions to display in which line
they occur. I use jhbuild with CFLAGS just set to "-g". Does somebody know what
the number after nautilus means. In my case the 6049.  

Thanks

Jaap


Comment 8 Kjartan Maraas 2005-03-03 23:25:24 UTC
I think the number after nautilus: is the pid, so it's not of importance. To get
a backtrace when these happen I think running with --g-fatal-warnings in gdb
will help. Optionally break on g_log or something.
Comment 9 Jaap A. Haitsma 2005-07-16 17:24:00 UTC
I think this bug can be closed
Comment 10 Kjartan Maraas 2005-07-24 16:46:59 UTC
Ok.
Comment 11 drago01 2007-06-10 19:27:37 UTC
please reopen this bug I see the same on F7 x86_64 with nautilus-2.18.1-2.fc7.
here is the error message:
--- Hash table keys for warning below:
--> file:///home/dragoran

(nautilus:5488): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)