20,864 bytes in 1 blocks are still reachable in loss record 3,996 of 3,996
==8805== at 0x402425F: calloc (vg_replace_malloc.c:467)
==8805== by 0x501FFB0: xcb_connect_to_fd (in /usr/lib/libxcb.so.1.1.0)
==8805== by 0x5022E5B: xcb_connect_to_display_with_auth_info (in /usr/lib/libxcb.so.1.1.0)
==8805== by 0x502314B: xcb_connect (in /usr/lib/libxcb.so.1.1.0)
==8805== by 0x49B4102: _XConnectXCB (in /usr/lib/libX11.so.6.3.0)
==8805== by 0x499BF0E: XOpenDisplay (in /usr/lib/libX11.so.6.3.0)
==8805== by 0x45226B3: gdk_display_open (in /usr/lib/libgdk-x11-2.0.so.0.2000.0)
==8805== by 0x44F0654: gdk_display_open_default_libgtk_only (in /usr/lib/libgdk-x11-2.0.so.0.2000.0)
==8805== by 0x423BC3E: ??? (in /usr/lib/libgtk-x11-2.0.so.0.2000.0)
==8805== by 0x47C9BDF: g_option_context_parse (in /lib/libglib-2.0.so.0.2400.1)
==8805== by 0x80814AC: main (nautilus-main.c:420
Nautilus fails to start properly in gnome session.
I Getting this message too. I did a debug with valgrind and there is a memory leak
http:// paste.ubuntu. com/437412/
20,864 bytes in 1 blocks are still reachable in loss record 3,996 of 3,996 malloc. c:467) libxcb. so.1.1. 0) to_display_ with_auth_ info (in /usr/lib/ libxcb. so.1.1. 0) libxcb. so.1.1. 0) libX11. so.6.3. 0) libX11. so.6.3. 0) libgdk- x11-2.0. so.0.2000. 0) open_default_ libgtk_ only (in /usr/lib/ libgdk- x11-2.0. so.0.2000. 0) libgtk- x11-2.0. so.0.2000. 0) context_ parse (in /lib/libglib- 2.0.so. 0.2400. 1) main.c: 420
==8805== at 0x402425F: calloc (vg_replace_
==8805== by 0x501FFB0: xcb_connect_to_fd (in /usr/lib/
==8805== by 0x5022E5B: xcb_connect_
==8805== by 0x502314B: xcb_connect (in /usr/lib/
==8805== by 0x49B4102: _XConnectXCB (in /usr/lib/
==8805== by 0x499BF0E: XOpenDisplay (in /usr/lib/
==8805== by 0x45226B3: gdk_display_open (in /usr/lib/
==8805== by 0x44F0654: gdk_display_
==8805== by 0x423BC3E: ??? (in /usr/lib/
==8805== by 0x47C9BDF: g_option_
==8805== by 0x80814AC: main (nautilus-
Nautilus fails to start properly in gnome session.
Top shows that it is maxing out the CPU