Version: (using KDE Devel) Installed from: Compiled sources OS: Linux KIO::Get job sometimes freeze. For example in krusader's functions Split File & Combine File. I think problem is in SocketConnectionBackend::socketReadyRead method (kdelibs/kio/kio/connection.h). The method checks socket->bytesAvailable() to make sure it could read complete message at once. But sometimes QSocket can't get more data from underlying connection until it's buffer is emptied. When I changed this method to read data into my buffer as soon as they are available, krusader no longer freezed.
Created attachment 22287 [details] Patch
First of all, please don't include whitespace changes in the patch. It makes a lot harder to read. Second, I am not sure I can accept your patch. With it, the connection would keep on reading even though the connection is suspended. The real question to be asked here is: why was the connection suspended if we're waiting for stuff to be read? Unless you're looking at the fact that setReadBufferSize in QTcpSocket does not trigger reading again. This is fixed in Qt 4.4.
Sorry for the whitespaces. I think the connection is suspended because socket received so much data than it didn't fit into its buffer. I seems than in this case socket waits until its buffer is completely empty before it starts reading again. I noticed this when I changed connection to use TCP sockets. When I watched packets in wireshark I noticed than when connection freeze there is Window full packet followed by lots of Zero Window packets. I don't know how to watch local sockets, but it appeared than the patch fixed it for local sockets too.
Is this applicable to KDE 4's KIO code?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!