Bug 454590 – 2.18: crash in fm_tree_model_unref_node at fm-tree-model.c:1531

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 454590 - 2.18: crash in fm_tree_model_unref_node at fm-tree-model.c:1531


Summary:	2.18: crash in fm_tree_model_unref_node at fm-tree-model.c:1531


Status:	RESOLVED DUPLICATE of bug 356672

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-07 14:37 UTC by Alexey Morlender
Modified:	2008-03-23 11:53 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Alexey Morlender 2007-07-07 14:37:58 UTC

Version: 2.18.1

What were you doing when the application crashed?
Pressed the "Up errow" button while navigating the Home folder.


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.2 2007-06-28 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-rc4 #1 SMP Wed Jun 6 17:44:48 EEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 305209344 vsize: 305209344 resident: 58875904 share: 44322816 rss: 58875904 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183799922 rtime: 1921 utime: 1690 stime: 231 cutime:53 cstime: 23 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47409471489376 (LWP 5715)]
[New Thread 1082132800 (LWP 29010)]
0x00002b1e5f54b53e in __libc_waitpid (pid=19565, stat_loc=0x7fff4fef0ffc, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 146340

Thread 1 (Thread 47409471489376 (LWP 5715))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#2 <signal handler called>
#3 IA__g_logv
#4 IA__g_log
at gmessages.c line 517
#5 IA__g_assert_warning
at gmessages.c line 552
#6 fm_tree_model_unref_node
at fm-tree-model.c line 1531
#7 gtk_tree_model_sort_real_unref_node
at gtktreemodelsort.c line 1243
#8 gtk_tree_row_reference_unref_path_helper
at gtktreemodel.c line 1860
#9 gtk_tree_row_reference_unref_path
at gtktreemodel.c line 1874
#10 IA__gtk_tree_row_reference_free
at gtktreemodel.c line 2101
#11 gtk_tree_selection_real_unselect_all
at gtktreeselection.c line 1043
#12 _gtk_tree_selection_internal_select_node
at gtktreeselection.c line 1318
#13 gtk_tree_view_real_set_cursor
at gtktreeview.c line 12255
#14 IA__gtk_tree_view_set_cursor_on_cell
at gtktreeview.c line 12383
#15 show_selection_idle_callback
at fm-tree-view.c line 242
#16 IA__g_main_context_dispatch
at gmain.c line 2045
#17 g_main_context_iterate
at gmain.c line 2677
#18 IA__g_main_loop_run
at gmain.c line 2881
#19 IA__gtk_main
at gtkmain.c line 1154
#20 main
at nautilus-main.c line 548



----------- .xsession-errors (17923 sec old) ---------------------
g_log: file dbus-server.c: line 713 (gaim_dbus_message_append_gaim_values): should not be reached
g_log: file dbus-server.c: line 713 (gaim_dbus_message_append_gaim_values): should not be reached
yahoo: 47 bytes to read, rxlen is 67
yahoo: Yahoo Service: 0x06 Status: 4
yahoo: Key: 5  	Value: viktor_volkov2000
yahoo: Key: 10  	Value: 99
yahoo: Key: 19  	Value: -1615400829
yahoo: 185 bytes to read, rxlen is 205
yahoo: Yahoo Service: 0x06 Status: 1
yahoo: Key: 5  	Value: a_morlender
yahoo: Key: 4  	Value: alexander_francuzov
yahoo: Key: 206  	Value: 2
yahoo: Key: 252  	Value: zLTBK4XB8QPsCY9UMOFyEX9IwN632g==
yahoo: Key: 97  	
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-03-23 11:53:57 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 356672 ***