From kde-devel Sun Oct 14 17:59:36 2007 From: Vlad Codrea Date: Sun, 14 Oct 2007 17:59:36 +0000 To: kde-devel Subject: Re: KIO::listDir() freezes in multi-threaded KioFuse due to timer Message-Id: <820930.72216.qm () web54402 ! mail ! yahoo ! com> X-MARC-Message: https://marc.info/?l=kde-devel&m=119238482526931 --- Thiago Macieira wrote: > Vlad Codrea wrote: > >KioFuse freezes and gives the following warning when Fuse is > allowed > >to create a separate thread for every filesystem operation. The > first > >readdir() attempt succeeds, but the freeze and warning appear > >consistently on the second readdir() attempt: > > Solution: use KIO from the GUI thread only. This seems to be an artificial limitation, since KIO and the GUI don't have much in common. There are apps, like KioFuse, that need file access but not a GUI. I thought that separating the GUI and non-GUI parts of KIO would have gotten rid of the GUI-thread limitation (http://websvn.kde.org/?view=rev&revision=632925). I can modify KioFuse to use KIO from the main thread, but that will add complexity to the program. I wonder if it would be better for me to try to make KIO usable from non-GUI threads, especially since other apps might need this, too. Just to be clear, I'm not talking about making KIO threadsafe (ie. using the same ListJob instance in multiple threads), but simply being able to create/use a ListJob instance in a non-GUI worker thread. Do you think this is feasible and worthwhile? Thanks, Vlad ____________________________________________________________________________________ Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.com/ >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<