On Tuesday 06 February 2007 02:29, Scott C. Frase wrote: > Thread 10 (Thread 2047089584 (LWP 6752)): > #0 0x082a634c in WaveCacheItem::get_size (this=0x981d220) at > wavecache.C:18 > #1 0x0813fded in CacheBase::get_memory_usage (this=0x8c04068) at > cachebase.C:152 > #2 0x081eff7b in MWindow::age_caches (this=0xbfc5a288) at > mwindow.C:1559 > #3 0x081f08d3 in MWindow::update_project (this=0xbfc5a288, load_mode=3) > at mwindow.C:1852 > #4 0x081f301c in MWindow::load_filenames (this=0xbfc5a288, > filenames=0x7a0413e8, load_mode=3, update_filename=0, > reel_name=0x82eb360 "none", > reel_number=-1, overwrite_reel=0) at mwindow.C:1133 > #5 0x081c8276 in LoadFileThread::run (this=0x8c68020) at loadfile.C:149 > #6 0xb7b88bb8 in Thread::entrypoint (parameters=0x8c68020) at > thread.C:48 > #7 0x00da0b80 in start_thread () from /lib/libpthread.so.0 > #8 0x00c11dee in clone () from /lib/libc.so.6
This is the interesting piece. Your last post also showed that a thread was working in MWindow::age_caches(). Next time, you have a hang can you please go to this thread and see which function takes so long to finish? age_caches() has 4 calls to get_memory_usage around line 1559. It's easiest if you use KDbg. Attach to the hanging process, Look up the thread in the Thread window, then use Execute->Step Into and ->Step out; I suspect that one of these functions takes long to complete; you will notice it when Step Out takes a while to come back. Welcome to the Hacker's guilde! ;) -- Hannes _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
