Bug#446598: nautilus: Nautilus randomly takes 100% of CPU

[giggzounet]

Josselin Mouette a écrit :
> Hi, and sorry for the overly long delay.
> 
> Le samedi 10 novembre 2007 à 18:29 +0100, giggzounet a écrit :
> 
>> Thread 1 (Thread 0xb6b8a6c0 (LWP 4368)):
>> #0  write_string (filename=0x8879d78
>> "/home/giggz/nautilus-debug-log.txt", file=0x8879dc0,
>>     str=0x856b6a0 "0x8174bc8 2007/11/10 18:21:09.8977 (USER): debug log
>> dumped due to signal 11", error=0x0) at nautilus-debug-log.c:446
>> No locals.
>> #1  0x080e2894 in nautilus_debug_log_dump (filename=0x8879d78
>> "/home/giggz/nautilus-debug-log.txt", error=0x0) at nautilus-debug-log.c:508
>>         file = (FILE *) 0x8879dc0
>>         success = <value optimized out>
>>         __PRETTY_FUNCTION__ = "nautilus_debug_log_dump"
>> #2  0x0807e9d6 in dump_debug_log () at nautilus-main.c:213
>> No locals.
>> #3  0x0807ea1f in sigfatal_handler (sig=11) at nautilus-main.c:258
>>         func = <value optimized out>
>> #4  <signal handler called>
>> No symbol table info available.
>> #5  magazine_cache_push_magazine (ix=1, magazine_chunks=<value optimized
>> out>, count=51) at /tmp/buildd/glib2.0-2.14.2/glib/gslice.c:470
>>         current = (ChunkLink *) 0x81c1020
>>         next = <value optimized out>
>>         prev = <value optimized out>
>> #6  0xb758a435 in thread_memory_magazine2_unload (tmem=<value optimized
>> out>, ix=0) at /tmp/buildd/glib2.0-2.14.2/glib/gslice.c:744
>>         mag = (Magazine *) 0x8175698
>> #7  0xb758bf37 in IA__g_slice_free_chain_with_offset (mem_size=12,
>> mem_chain=0x81ae200, next_offset=4) at
>> /tmp/buildd/glib2.0-2.14.2/glib/gslice.c:928
>>         current = (guint8 *) 0x81ae200 "\001"
>>         tmem = (ThreadMemory *) 0x8175290
>>         ix = 1
>>         slice = (gpointer) 0x81ae210
>>         chunk_size = 16
>> #8  0xb756d461 in IA__g_list_free (list=0x81ae200) at
>> /tmp/buildd/glib2.0-2.14.2/glib/glist.c:53
>> No locals.
>> #9  0xb7f1239f in eel_enumeration_free () from /usr/lib/libeel-2-2.20.so
>> No symbol table info available.
>> #10 0xb7f123fa in ?? () from /usr/lib/libeel-2-2.20.so
>> No symbol table info available.
> 
> Unfortunately we cannot see what is causing this because it must be in
> libeel. Could you please rebuild it with debugging symbols and try
> again?
> 


Hi,

just to tell you that the problem doesn't appear again...but I don't
know why...since my home crashes and I recup it, I don't have any
problem. So perhaps a config file...

Cheers,
Guillaume

> Thanks,