KURLCompletion & chdir from thread
Waldo Bastian
bastian at kde.org
Mon Dec 20 13:01:20 GMT 2004
It occured to me that KURLCompletion's use of QDir::setCurrent() is not very
safe since it affects the whole process and not just the thread.
See e.g. http://twomix.devolution.com/pipermail/sdl/2004-March/060615.html
In particular Konqueror may start a new process while the KURLCompletion
thread is still running with CWD set to the current URL instead of the
default CWD ($HOME) This may cause such process to keep a mount point
occupied.
Cheers,
Waldo
--
bastian at kde.org | Free Novell Linux Desktop 9 Evaluation Download
bastian at suse.com | http://www.novell.com/products/desktop/eval.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20041220/2f11de4f/attachment.sig>
More information about the kde-core-devel
mailing list