! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Toggling Hidden Directory Thunar Crashes/Freezes
Status:
RESOLVED: WORKSFORME

Comments

Description nai 2009-01-23 10:06:22 CET
Gateway 3018GZ Laptop
Slackware 12.2
Kernel 2.6.27.7-SMP
XFCE 4.4.3
Thunar 0.9.3

I was able to reproduce the following 2 bugs many times. The results came out to random freezing and crashes. But after killing the process, thunar was still usable as long as I don't toggle the .hidden directory or directories.

With the following enabled in thunar under "view" options:

- toolbar style
- statusbar
- view as compact list
- tree (optional - it'll crash regardless if it's enabled)

To reproduce this I did the following:

NOTE: At least one file must be present in the .hidden directory. Size of file does not matter.

1. open one thunar
2. access and open any .hidden directory from the toolbar
3. click and bring down the toolbar list and try to click and open the same .hidden directory
4. thunar will crash...
--------------------------------------------------------------------------

I was able to reproduce a freeze in thunar.

With the following enabled in thunar under "view" options:

- toolbar style
- statusbar
- view as compact list
- tree

1. access and open .hidden directory from the toolbar.
2. click and toggle back and forth between the .hidden directory and any directory on the left tree pane.
3. thunar will freeze.
4. If you have the trash can on your desktop panel, it'll change into an icon that looks like a stop sign. Kill the thunar process and hover your mouse over the trash can, it'll go away and change back to normal.
Comment 1 Nick Schermer editbugs 2009-01-23 13:44:16 CET
Haven't tried to reproduce this, but can you provide a backtrace (compile with debugging, gdb thunar, run, bt)?
Comment 2 nai 2009-01-24 03:49:06 CET
To tell you the truth, I'm not completely sure on how to run gdb and backtrace. But from reading the man page, and after running a few commands and trying to reproduce the first bug on the list, this is what I got:

[Thread debugging using libthread_db enabled]
[New Thread 0xb740b700 (LWP 3871)]
[New Thread 0xb72b6b90 (LWP 3874)]
[New Thread 0xb6ab6b90 (LWP 3875)]
[New Thread 0xb62b6b90 (LWP 3876)]
[New Thread 0xb5ab6b90 (LWP 3877)]
[New Thread 0xb52b6b90 (LWP 3878)]
[New Thread 0xb4ab6b90 (LWP 3879)]
[New Thread 0xb42b6b90 (LWP 3880)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread 0xb72b6b90 (LWP 3874) exited]
[Thread 0xb6ab6b90 (LWP 3875) exited]
[Thread 0xb62b6b90 (LWP 3876) exited]
[Thread 0xb5ab6b90 (LWP 3877) exited]
[New Thread 0xb62b6b90 (LWP 3881)]
[New Thread 0xb5ab6b90 (LWP 3882)]
[New Thread 0xb6ab6b90 (LWP 3883)]
[New Thread 0xb72b6b90 (LWP 3884)]
[New Thread 0xb3a9eb90 (LWP 3885)]
[New Thread 0xb329eb90 (LWP 3886)]
[New Thread 0xb2a9eb90 (LWP 3887)]
[New Thread 0xb229eb90 (LWP 3888)]
[New Thread 0xb1a9eb90 (LWP 3889)]
[New Thread 0xb129eb90 (LWP 3890)]
[Thread 0xb5ab6b90 (LWP 3882) exited]
[Thread 0xb1a9eb90 (LWP 3889) exited]
[New Thread 0xb1a9eb90 (LWP 3891)]
[New Thread 0xb5ab6b90 (LWP 3892)]
[New Thread 0xb0a9eb90 (LWP 3893)]
[Thread 0xb5ab6b90 (LWP 3892) exited]
[Thread 0xb129eb90 (LWP 3890) exited]
[Thread 0xb6ab6b90 (LWP 3883) exited]
[Thread 0xb3a9eb90 (LWP 3885) exited]
[Thread 0xb2a9eb90 (LWP 3887) exited]
[Thread 0xb62b6b90 (LWP 3881) exited]
[Thread 0xb229eb90 (LWP 3888) exited]
[Thread 0xb4ab6b90 (LWP 3879) exited]
[Thread 0xb52b6b90 (LWP 3878) exited]
[Thread 0xb42b6b90 (LWP 3880) exited]
[Thread 0xb329eb90 (LWP 3886) exited]

(thunar:3871): Gtk-CRITICAL **: gtk_tree_model_get: assertion `GTK_IS_TREE_MODEL (tree_model)' failed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb740b700 (LWP 3871)]
0x0807ccce in ?? ()
(gdb) backtrace
#0  0x0807ccce in ?? ()
#1  0x00000000 in ?? ()
--------------------------------------------------------------------------------------------

After trying to test out the second bug, this is what I got from gdb. Thunar and gdb froze and I couldn't do much, so I killed the thunar process and gdb was back up and running, then I ran backtrace:

[Thread debugging using libthread_db enabled]
[New Thread 0xb737c700 (LWP 3951)]
[New Thread 0xb7227b90 (LWP 3954)]
[New Thread 0xb6a27b90 (LWP 3955)]
[New Thread 0xb6227b90 (LWP 3956)]
[New Thread 0xb5a27b90 (LWP 3957)]
[New Thread 0xb5227b90 (LWP 3958)]
[New Thread 0xb4a27b90 (LWP 3959)]
[New Thread 0xb4227b90 (LWP 3960)]
[Thread 0xb7227b90 (LWP 3954) exited]
[Thread 0xb6227b90 (LWP 3956) exited]
[Thread 0xb6a27b90 (LWP 3955) exited]
[Thread 0xb5a27b90 (LWP 3957) exited]
[New Thread 0xb6227b90 (LWP 3961)]
[New Thread 0xb5a27b90 (LWP 3962)]
[New Thread 0xb6a27b90 (LWP 3963)]
[New Thread 0xb7227b90 (LWP 3964)]
[New Thread 0xb3a0fb90 (LWP 3965)]
[New Thread 0xb320fb90 (LWP 3966)]
[New Thread 0xb2a0fb90 (LWP 3967)]
[New Thread 0xb220fb90 (LWP 3968)]
[New Thread 0xb1a0fb90 (LWP 3969)]
[Thread 0xb220fb90 (LWP 3968) exited]
[New Thread 0xb220fb90 (LWP 3970)]
[Thread 0xb2a0fb90 (LWP 3967) exited]
[New Thread 0xb2a0fb90 (LWP 3971)]
[Thread 0xb2a0fb90 (LWP 3971) exited]
[New Thread 0xb2a0fb90 (LWP 3972)]
[New Thread 0xb120fb90 (LWP 3973)]
[New Thread 0xb0a0fb90 (LWP 3974)]
[New Thread 0xb020fb90 (LWP 3975)]
[Thread 0xb020fb90 (LWP 3975) exited]
[Thread 0xb1a0fb90 (LWP 3969) exited]
[Thread 0xb220fb90 (LWP 3970) exited]
[Thread 0xb120fb90 (LWP 3973) exited]
[Thread 0xb7227b90 (LWP 3964) exited]
[Thread 0xb6a27b90 (LWP 3963) exited]
[Thread 0xb4227b90 (LWP 3960) exited]
[Thread 0xb5a27b90 (LWP 3962) exited]
[Thread 0xb3a0fb90 (LWP 3965) exited]
[Thread 0xb4a27b90 (LWP 3959) exited]
[Thread 0xb5227b90 (LWP 3958) exited]
[Thread 0xb6227b90 (LWP 3961) exited]
[New Thread 0xb6227b90 (LWP 3976)]
[New Thread 0xb4a27b90 (LWP 3977)]
[New Thread 0xb5227b90 (LWP 3978)]
[New Thread 0xb5a27b90 (LWP 3979)]
[New Thread 0xb3a0fb90 (LWP 3980)]
[New Thread 0xb7227b90 (LWP 3981)]
[New Thread 0xb6a27b90 (LWP 3982)]
[New Thread 0xb4227b90 (LWP 3983)]
[New Thread 0xb220fb90 (LWP 3984)]
[Thread 0xb6a27b90 (LWP 3982) exited]
[New Thread 0xb6a27b90 (LWP 3985)]
[Thread 0xb6a27b90 (LWP 3985) exited]
[New Thread 0xb6a27b90 (LWP 3986)]
[New Thread 0xb1a0fb90 (LWP 3987)]
[Thread 0xb6a27b90 (LWP 3986) exited]
[Thread 0xb1a0fb90 (LWP 3987) exited]
[New Thread 0xb1a0fb90 (LWP 3988)]
[Thread 0xb220fb90 (LWP 3984) exited]
[New Thread 0xb220fb90 (LWP 3989)]
[New Thread 0xb6a27b90 (LWP 3990)]
[New Thread 0xb020fb90 (LWP 3991)]
[Thread 0xb6a27b90 (LWP 3990) exited]
[Thread 0xb4227b90 (LWP 3983) exited]
[Thread 0xb220fb90 (LWP 3989) exited]
[New Thread 0xb220fb90 (LWP 3992)]
[Thread 0xb1a0fb90 (LWP 3988) exited]
[Thread 0xb220fb90 (LWP 3992) exited]
[Thread 0xb020fb90 (LWP 3991) exited]
[Thread 0xb7227b90 (LWP 3981) exited]
Program received signal SIGTERM, Terminated.
[Switching to Thread 0xb737c700 (LWP 3951)]
0xb798d2c1 in write () from /lib/libpthread.so.0
(gdb) backtrace
#0  0xb798d2c1 in write () from /lib/libpthread.so.0
#1  0xb75b585d in ?? () from /usr/lib/libgamin-1.so.0
#2  0x0000000a in ?? ()
#3  0xbfafc362 in ?? ()
#4  0x00000024 in ?? ()
#5  0xb75b583e in ?? () from /usr/lib/libgamin-1.so.0
#6  0x00000001 in ?? ()
#7  0x0876b698 in ?? ()
#8  0xbfafd388 in ?? ()
#9  0xb75b5a50 in ?? () from /usr/lib/libgamin-1.so.0
#10 0x00000024 in ?? ()
#11 0xb75ba114 in ?? () from /usr/lib/libgamin-1.so.0
#12 0xbfafd388 in ?? ()
#13 0xb75b5b0a in ?? () from /usr/lib/libgamin-1.so.0
#14 0x0000000a in ?? ()
#15 0xbfafc362 in ?? ()
#16 0x00000024 in ?? ()
#17 0xb75b593a in ?? () from /usr/lib/libgamin-1.so.0
#18 0x0838fc50 in ?? ()
#19 0xbfafc614 in ?? ()
#20 0x00000003 in ?? ()
#21 0x00000000 in ?? ()
Comment 3 Nick Schermer editbugs 2009-01-25 12:14:51 CET
Fixed the first crash in revision 29340, duno if it will make it in xfce4.6rc1.

The seconds one i can't reproduce. Could you give a more detailed description? What kind of directory (a lot of activity inside it)? When you kill gam_server, does it help?
Comment 4 nai 2009-01-26 05:34:34 CET
To be truthful, this isn't a really big issue for me. Thunar is still usable and I can take advantage of it as long as I don't mess around and toggle the hidden directories. Anyway, on we go...

I apologize I wasn't very thorough on the second bug. I will be attempting to test the second bug on two machines to determine if size is a facter. For this first attempt, I have 6.3gb size in my /home/name directory. To be specific, the following folders and files were created in my /home/name directory, the steps include:

1st attempt...

cd /home/name
mkdir .sample <-- sample folder contains a text file.
mkdir sample <-- sample folder contains a text file.
cd /home/name/sample
mkdir test <-- test folder contains a text file.

I restarted the computer just to make sure that everything was loaded. Then I did the following to make thunar freeze:

With the following enabled in thunar under "view" options:

- toolbar style
- statusbar
- view as compact list
- tree

1. access and open .hidden directory from the toolbar.
2. click and toggle back and forth between the .sample folder and the 2nd sample folder on the left tree pane a few times(about 4-6 mouse clicks)
3. close thunar and open it back up. Thunar will take awhile just to load all the contents in the working directory.
4. Repeat step #2 and thunar will freeze.

When it froze, I killed the "/usr/bin/Thunar --daemon" process and restarted thunar and it was working again. I wanted to make sure that what I was doing was correct and so I started back at step #1 to try and reproduce the bug. And again, thunar froze.
----------------------------------------------------------------------------

2nd method...

Second attempt on a different test machine but this time /home/name directory has a total size of 224mb. After trying to replicate and mimic the above steps, thunar froze but not for too long--sometimes it would close and sometimes I had to kill the process "/usr/bin/Thunar --daemon", then after restarting thunar it would work as usual as long as I didn't repeat step #2 and toggle back and forth. Prior to all of this, I never touched gam_server because I felt I didn't have the need to.

After testing 2 methods on the second bug, I can conclude that it's somewhat of a size issue. For the first method, the system had over 6gigs of data in /home/name which lead thunar to literally freeze. But on the second method, the system had only 224mb of data in /home/name which lead thunar to freeze but not for very long--it would freeze for awhile and sometimes come back to normal. A bit buggy for people who work with hidden directories.

Hope that helps :)=
Comment 5 Jannis Pohlmann editbugs 2010-11-13 17:25:36 CET
Does this second issue still exist in the GIO version of Thunar (>= 1.1.0)? I cannot reproduce it. I'm closing it with WORKSFORME for now. Please re-open if this is still not working yet.

Bug #4847

Reported by:
nai
Reported on: 2009-01-23
Last modified on: 2010-11-13

People

Assignee:
Jannis Pohlmann
CC List:
1 user

Version

Version:
0.9.93 (1.0beta3)

Attachments

Additional information