| Summary: | kio_http runs with 100 % cpu load | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Jonas <bugs.kde.j> |
| Component: | kdeinit | Assignee: | Andreas Hartmetz <ahartmetz> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | adam, ahartmetz, alieneye, bugs.kde.org.agq36, cannewilson, contact, dglent, lanx, makmichalis, mark0d0da, menegola, metrobotte, mkyral, mpyne, pfmiller, tightcode, wmhilton, yuri |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
kio_http gdb backtrace
GDB backtraces from kio_http gdb kio_http backtrace |
||
|
Description
Jonas
2009-02-01 20:24:53 UTC
I can confirm this, in KDE 4.2 precompiled kubuntu-experimental packages (Versión 4.2.00) using Ubuntu 8.10. With only 1 process I also have a 100% CPU load. I confirm the same problem in Mandriva 2009.1 (kde 4.2.0) Removing yaWP (Yet Another Weather Plasmoid) solves this issue for me, until this problem is "really" fixed! Most of time it works correctly, but from time to time, probably on some special conditions kio_http process didn't finish but stays and uses 100% of CPU.
Strace -p <pid> shows nothing.
gdb kio_http <pid> give this backtrace:
#0 0x00000036efa03976 in gzread () from /lib/libz.so.1
#1 0x00007f04d67f4b70 in HTTPProtocol::readBody (this=0x7fffdef12e30, dataInternal=false)
at /var/tmp/portage/kde-base/kdelibs-4.2.0-r2/work/kdelibs-4.2.0/kioslave/http/http.cpp:4077
#2 0x00007f04d6801bfc in HTTPProtocol::proceedUntilResponseContent (this=0x7fffdef12e30, dataInternal=80)
at /var/tmp/portage/kde-base/kdelibs-4.2.0-r2/work/kdelibs-4.2.0/kioslave/http/http.cpp:517
#3 0x00007f04d68026b2 in HTTPProtocol::get (this=0x7fffdef12e30, url=@0x7fffdef12c40)
at /var/tmp/portage/kde-base/kdelibs-4.2.0-r2/work/kdelibs-4.2.0/kioslave/http/http.cpp:1195
#4 0x00000036fe778287 in KIO::SlaveBase::dispatch (this=<value optimized out>, command=<value optimized out>, data=<value optimized out>)
at /var/tmp/portage/kde-base/kdelibs-4.2.0-r2/work/kdelibs-4.2.0/kio/kio/slavebase.cpp:1035
#5 0x00000036fe778854 in KIO::SlaveBase::dispatchLoop (this=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.2.0-r2/work/kdelibs-4.2.0/kio/kio/slavebase.cpp:282
#6 0x00007f04d67fbc92 in kdemain (argc=4, argv=0x1914760) at /var/tmp/portage/kde-base/kdelibs-4.2.0-r2/work/kdelibs-4.2.0/kioslave/http/http.cpp:109
#7 0x0000000000406c59 in launch (argc=4, _name=0x192bba8 "kio_http", args=0x192bc20 "", cwd=0x0, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0,
avoid_loops=false, startup_id_str=0x40ab9c "0") at /var/tmp/portage/kde-base/kdelibs-4.2.0-r2/work/kdelibs-4.2.0/kinit/kinit.cpp:690
#8 0x000000000040775e in handle_launcher_request (sock=7) at /var/tmp/portage/kde-base/kdelibs-4.2.0-r2/work/kdelibs-4.2.0/kinit/kinit.cpp:1270
#9 0x0000000000407ed6 in handle_requests (waitForPid=0) at /var/tmp/portage/kde-base/kdelibs-4.2.0-r2/work/kdelibs-4.2.0/kinit/kinit.cpp:1463
#10 0x0000000000408409 in main (argc=2, argv=0x7fffdef139d8, envp=0x7fffdef139f0) at /var/tmp/portage/kde-base/kdelibs-4.2.0-r2/work/kdelibs-4.2.0/kinit/kinit.cpp:1939
*** This bug has been confirmed by popular vote. *** I'm using KDE 4.2.1 and Qt 4.5.0 and this bug seems to be solved. (In reply to comment #6) > I'm using KDE 4.2.1 and Qt 4.5.0 and this bug seems to be solved. KDE 4.2.2, qt 4.5.1. I use archlinux with kdemod packages, everything is up to date, i used the yet another weather plasmoid, and kio_http was using 100% of the system, removed the plasmoid, loged out, loged in and now i don't have that problem anymore. So i guess it is a problem of the plasmoid http://tinyurl.com/c6wdhr (In reply to comment #7) > (In reply to comment #6) > > I'm using KDE 4.2.1 and Qt 4.5.0 and this bug seems to be solved. > > KDE 4.2.2, qt 4.5.1. > I use archlinux with kdemod packages, everything is up to date, i used the yet > another weather plasmoid, and kio_http was using 100% of the system, removed > the plasmoid, loged out, loged in and now i don't have that problem anymore. So > i guess it is a problem of the plasmoid http://tinyurl.com/c6wdhr Yes, I had this issues with 4.2.2 as well. There is regression in 4.2.2. Gentoo and probably some other distributions have fixed it. http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=commit;h=c1657311b5ad04e24dd8178e051e5cd5c905bae4 I also am getting runaway kio_http processes that take up 100% CPU and drive my fan wild to cool the laptop down. Am also using yaWP (Yet Another Weather Plasmoid). Interestingly, the changelog for version 2.2 says: "* Removed obsolete KIO workaround". I guess that workaround is not so obsolete. Is this really a regression? Why? Kubuntu 9.04 Qt: 4.5.0 KDE: 4.2.2 (KDE 4.2.2) kde4-config: 1.0 (In reply to comment #9) > I also am getting runaway kio_http processes that take up 100% CPU and drive my > fan wild to cool the laptop down. Am also using yaWP (Yet Another Weather > Plasmoid). Interestingly, the changelog for version 2.2 says: "* Removed > obsolete KIO workaround". I guess that workaround is not so obsolete. Is this > really a regression? Why? > > Kubuntu 9.04 > Qt: 4.5.0 > KDE: 4.2.2 (KDE 4.2.2) > kde4-config: 1.0 Why it is a reggresion? I don't have this problem in 4.2.1. But I have the 100% kio issue back right after installation of 4.2.2. And it dissapear after installation of updated kdelibs. So, please wait for 4.2.3, it is comming soon and should be fixed. @ Marian Kyral: I should have been more clear. What I meant was, if there was a regression, what was the cause? Was it a mistake, or what was the reason that the problem came back? In fact I did not investigated it deeply. Check this patch for details: http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=kde-base/kdelibs/files/kdelibs-4.2-fix_kio_http_401.patch;h=d6734f44dc1c474ee0595991a2f03eed731e2462;hb=c1657311b5ad04e24dd8178e051e5cd5c905bae4 Created attachment 33955 [details]
kio_http gdb backtrace
Sorry I forget to add the comment to backtrace, well I still have this problem on KDE 4.2.3 (Fedora 10). @lanx@o2.pl: Yes, unfortunately is the issue back :-( I still don't know what exactly is wrong. Cannot find the right conditions to reproduce it regularly. What type of network connection are you using? And how many yawp apllets have you on desktop/panel? BTW: the backtrace is not useless. Only 1 yawp and actually it's the only one component which connetcs to network via kde, usally I use Firefox browser. This time it happend during second yawp refresh after 15 minutes, maybe it's the way which yawp uses kio_http or target site (weather data). Just quessing, I didn't take a look at yawp code. I tried hard but I could not get this error using Konqueror. I can verify the problem is not fixed in KDE 4.2.3, Kubuntu 9.04 packages. Using two yaWP plasmoids. I will add that the problem seems to occur less frequently than it did before, and typically when my fan is on high enough for me to notice/catch the problem there are 3 kio_http processes. I'm not sure what causes it, because I have on occasion left the computer on overnight and not had this problem, but sometimes left the computer for only a few hours and it's there. (Using a WPA wirelless connection, Intel 3945 card.) Assigning to me. This should be fixed in trunk, as the gentoo patch linked earlier seems to be a change in trunk. In case we're going to release a 4.2.4 I'm going to backport the fix. I could have taken care of this much earlier, I just don't systematically search for bugs here that often. Sorry. *** Bug 193856 has been marked as a duplicate of this bug. *** Thanks. I'm one of developer. I checked our kio code and looks correct (according to tutorial). The issue was gone in 4.2.1 and 4.2.2 with patch. But now is back. In 4.2.3 (with patch) and 4.2.87. But is much less frequent then before. I've suspicion for some network connection issue, e.g. low quality wifi. So... I'm just dying of curiosity here. What exactly is kio_http doing/waiting for that makes it hog CPU so much? And more importantly, why does it only happen with yaWP? Is there a way the code can be restructured to prevent it from taking 100% CPU? For what it is worth, on Gentoo w/ KDE 4.2.4, this problem has returned. I have 4 yaWP widgets and this laptop gets uncomfortably hot as a result so I am disabling these plasmoids for the time being. I will keep an eye out for updated patches/resolutions. Kde 4.2.4,latest yawp(from svn) qt 4.5.1 same problem. 4 kio_http process go to 100% of cpu I tried now without yawp.. same problem. :( @JPD, @giuseppe Could you help us to find conditions to reproduce the bug? What connection to network are you using? Wifi? I'm using KDE 4.2.4 and 4.2.90 and it happen only once in last month. My connection is via 'Network over mains'. It is quite a slow connection but has worked OK for the past 18 months. Fixed for me. Solution :use yawp-0.2.3 from kde-look.org,NOT FROM SVN and reboot or restart kde(make sure all process killed and libs unused with ps and lsof). Not fixed..:( (In reply to comment #27) > Fixed for me. > Solution :use yawp-0.2.3 from kde-look.org,NOT FROM SVN > and reboot or restart kde(make sure all process killed and > libs unused with ps and lsof). Hem..is not fixed. :((( I have fast and stable connection, I also tested wireless connection on my D-Link router, so it's not the problem with connection. i have two systems with the same configuration in both of them 1) Desktop Mandriva 2009.1 KDE 4.2.2 - two yawp plasmoids - plasma-applet-yawp-0.2.3-1mdv2009.1 - ethernet 2) Laptop Mandriva 2009.1 KDE 4.2.2 - two yawp plasmoids - plasma-applet-yawp-0.2.1-3mdv2009.1 - wifi I have the problem ONLY in the desktop. It hapens once every 3-4 days. I have to kill the kio_http process to continue working on it. If it hapenns when i am not in front of the PC, i have to be connected with ssh from the laptop to kill the process because the CPU is totaly occupied, the fans turns in high speed and the mouse and the keybord dont responding. what kind of informations may i provide to find out the cause and the solution of this problem ? Maybe is the version of yawp ? is the only difference, but the users clamed with all (?) versions of yawp lanx@o2.pl: Thanks, so we can exclude connection. How many Yawp you have running? Because as far as I remember, there were always at least two kio_http processes. And is strange that there is more, independent YaWP processes and all of them has the same issue. Looks more like some specific issue on data, e.g. corrupted data sent by accuweather.com. Your and my backtraces shows #0 0x00000036efa03976 in gzread () from /lib/libz.so.1 Maybe is bug there? :-( Hi, (In reply to comment #30) > i have two systems with the same configuration in both of them > 1) Desktop Mandriva 2009.1 KDE 4.2.2 - two yawp plasmoids - > plasma-applet-yawp-0.2.3-1mdv2009.1 - ethernet > 2) Laptop Mandriva 2009.1 KDE 4.2.2 - two yawp plasmoids - > plasma-applet-yawp-0.2.1-3mdv2009.1 - wifi > > I have the problem ONLY in the desktop. It hapens once every 3-4 days. I have > to kill the kio_http process to continue working on it. If it hapenns when i am > not in front of the PC, i have to be connected with ssh from the laptop to kill > the process because the CPU is totaly occupied, the fans turns in high speed > and the mouse and the keybord dont responding. > > what kind of informations may i provide to find out the cause and the solution > of this problem ? > > > Maybe is the version of yawp ? is the only difference, but the users clamed > with all (?) versions of yawp Could you try plasma-applet-yawp-0.2.1-3mdv2009.1 on desktop? I think copy of the library could be enough. If it helps, then it is bug in YaWP and we can investigate the changes in YaWP, otherwise it could be a bug in kio_http or kio implementation in Yawp. I will try to create an patch to use qhhtp instead of kio. I did not get any kio_http running with 100% the last days. My configuration: yawp 0.23-1.2-x86_64 from suse rpm and kdelibs4-4.2.4.1-2.3 - KDE Base Libraries and I am using 2 yawp plasmoids. I hope it will help you I have tried also kde 4.2.91(beta2) with different versions of yawp Also tried with a clean .kde nothing..kio_http goes to 100% Well, I still get 100%, 2-4 kio_http processes. Kubuntu, KDE 4.2.4, three YaWPs. Wireless. Laptop. For now, I'm just giving up and will remove YaWP. If there is any way I can actually provide useful data for debugging, let me know. I confirm the same bug. kio_http used 100% CPU. I had one Yawp widget, removed the same and noticed kio_http doesnt use CPU resources anymore. I have been using Yawp for months now and today is the first time I came across this. *** Bug 191449 has been marked as a duplicate of this bug. *** *** Bug 186606 has been marked as a duplicate of this bug. *** Some instructions how you can help me find the bug. The idea is to interrupt the execution of the ioslave a couple of times and look what it's doing at that time. Chances are very high that you catch it in the loop where it wastes all the CPU time. - Install debug packages for the HTTP ioslave. This probably means debug packages for kdelibs since the HTTP ioslave's code lives in kdelibs. - Reproduce kio_http using 100% CPU. - Find out the PID of the kio_http process, start gdb (the debugger) and type "attach <PID>" - Continue execution with "cont" when the debug information has been loaded (gdb takes a while after you attach). - Maybe five times press control-c (to interrupt), bt<enter> (to get a backtrace), cont<enter> to continue. - Paste all the backtraces or if you want the whole gdb session here. Created attachment 34599 [details]
GDB backtraces from kio_http
Andreas, I just noticed my kio_http using all my CPU time and I just attached some GDB backtraces from it. I am running KDE 4.2.2. This is the first time in awhile that I've come across this bug. I have just installed the latest Mandriva updates on my other system running KDE 4.2.2 on Mandriva 2009.0 and the bug has now appeared on that! CPU was running at 100% and CPU temp around 78C! Closed YaWP, logged out and back in again and CPU now at about 10-15% and CPU temp back at 60C. (In reply to comment #32) > Hi, > (In reply to comment #30) > > i have two systems with the same configuration in both of them > > 1) Desktop Mandriva 2009.1 KDE 4.2.2 - two yawp plasmoids - > > plasma-applet-yawp-0.2.3-1mdv2009.1 - ethernet > > 2) Laptop Mandriva 2009.1 KDE 4.2.2 - two yawp plasmoids - > > plasma-applet-yawp-0.2.1-3mdv2009.1 - wifi > > > > I have the problem ONLY in the desktop. It hapens once every 3-4 days. I have > > to kill the kio_http process to continue working on it. If it hapenns when i am > > not in front of the PC, i have to be connected with ssh from the laptop to kill > > the process because the CPU is totaly occupied, the fans turns in high speed > > and the mouse and the keybord dont responding. > > > > what kind of informations may i provide to find out the cause and the solution > > of this problem ? > > > > > > Maybe is the version of yawp ? is the only difference, but the users clamed > > with all (?) versions of yawp > > Could you try plasma-applet-yawp-0.2.1-3mdv2009.1 on desktop? I think copy of > the library could be enough. If it helps, then it is bug in YaWP and we can > investigate the changes in YaWP, otherwise it could be a bug in kio_http or kio > implementation in Yawp. > > I will try to create an patch to use qhhtp instead of kio. since 11 june 2009 when i installed the yawp 0.2.1 i had the probleme only once. All I have to do is leave my laptop running and go out for dinner. By the time I come back, the fan will be humming like crazy, and my CPU and Temperature monitors will have flatlined at 100% and 73 deg C. This time it appears 3 kio_http's were responsible. Process 13312 taking about 80% and 13303 and 13308 each taking about 49%. (As reported by top - using a Intel Core 2 Duo.) Here are some backtraces, using the method from Comment #39. I've never done this before, so forgive me for pasting so many raw backtraces, but I read somewhere that pasting backtraces in comments was preferred over putting them in an attachment. I thought there might be some important differences between the threads, especially since one was taking 80% and the other two were taking 49%, and I wanted at least 5 backtraces for each thread. Again, this only appears to happen with YaWP running. $ uname -a Linux Swordfish 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux $ kde4-config --version Qt: 4.5.0 KDE: 4.2.4 (KDE 4.2.4) kde4-config: 1.0 ***************** * Process 13312 * ***************** Continuing. ^C Program received signal SIGINT, Interrupt. [Switching to Thread 0xb5f0ca10 (LWP 13312)] 0xb5d7c270 in gzeof@plt () from /usr/lib/kde4/kio_http.so (gdb) bt #0 0xb5d7c270 in gzeof@plt () from /usr/lib/kde4/kio_http.so #1 0xb5d97ce4 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4173 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=200) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x85b3a88) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 (gdb) cont Continuing. ^C Program received signal SIGINT, Interrupt. 0xb64d9726 in gzread () from /lib/libz.so.1 (gdb) bt #0 0xb64d9726 in gzread () from /lib/libz.so.1 #1 0xb5d97d12 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4175 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=200) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x85b3a88) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb5d97d00 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4175 4175 /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp: No such file or directory. in /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp Current language: auto; currently c++ (gdb) bt #0 0xb5d97d00 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4175 #1 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=252) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #2 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #3 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #4 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #5 0xb5d8bf5b in kdemain (argc=4, argv=0x85b3a88) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #6 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #7 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #8 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #9 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb5d7b460 in gzread@plt () from /usr/lib/kde4/kio_http.so Current language: auto; currently asm (gdb) bt #0 0xb5d7b460 in gzread@plt () from /usr/lib/kde4/kio_http.so #1 0xb5d97d12 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4175 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=200) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x85b3a88) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb64d8a30 in gzeof () from /lib/libz.so.1 (gdb) bt #0 0xb64d8a30 in gzeof () from /lib/libz.so.1 #1 0xb5d97ce4 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4173 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=200) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x85b3a88) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb64d95d1 in gzread () from /lib/libz.so.1 (gdb) bt #0 0xb64d95d1 in gzread () from /lib/libz.so.1 #1 0xb5d97d12 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4175 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=255) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x85b3a88) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 ***************** * Process 13308 * ***************** Continuing. ^C Program received signal SIGINT, Interrupt. [Switching to Thread 0xb5f0ca10 (LWP 13308)] 0xb5d7c270 in gzeof@plt () from /usr/lib/kde4/kio_http.so (gdb) bt #0 0xb5d7c270 in gzeof@plt () from /usr/lib/kde4/kio_http.so #1 0xb5d97ce4 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4173 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=160) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x85b4170) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb64d8a3e in gzeof () from /lib/libz.so.1 (gdb) bt #0 0xb64d8a3e in gzeof () from /lib/libz.so.1 #1 0xb5d97ce4 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4173 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=160) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x85b4170) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb64d9726 in gzread () from /lib/libz.so.1 (gdb) bt #0 0xb64d9726 in gzread () from /lib/libz.so.1 #1 0xb5d97d12 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4175 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=160) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x85b4170) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb64d8a3e in gzeof () from /lib/libz.so.1 (gdb) bt #0 0xb64d8a3e in gzeof () from /lib/libz.so.1 #1 0xb5d97ce4 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4173 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=160) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x85b4170) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb64d95a6 in gzread () from /lib/libz.so.1 (gdb) bt #0 0xb64d95a6 in gzread () from /lib/libz.so.1 #1 0xb5d97d12 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4175 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=160) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x85b4170) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 ***************** * Process 13303 * ***************** (gdb) bt #0 0xb5d97d0d in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4175 #1 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=80) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #2 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #3 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #4 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #5 0xb5d8bf5b in kdemain (argc=4, argv=0x859d548) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #6 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #7 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #8 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #9 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. [Switching to Thread 0xb5f0ca10 (LWP 13303)] 0xb64d8a48 in gzeof () from /lib/libz.so.1 (gdb) bt #0 0xb64d8a48 in gzeof () from /lib/libz.so.1 #1 0xb5d97ce4 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4173 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=80) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x859d548) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb5d7c270 in gzeof@plt () from /usr/lib/kde4/kio_http.so Current language: auto; currently asm (gdb) bt #0 0xb5d7c270 in gzeof@plt () from /usr/lib/kde4/kio_http.so #1 0xb5d97ce4 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4173 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=80) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x859d548) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb64d95de in gzread () from /lib/libz.so.1 (gdb) bt #0 0xb64d95de in gzread () from /lib/libz.so.1 #1 0xb5d97d12 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4175 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=80) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x859d548) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4177 4177 in /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp Current language: auto; currently c++ (gdb) bt #0 HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4177 #1 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=255) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #2 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #3 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #4 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #5 0xb5d8bf5b in kdemain (argc=4, argv=0x859d548) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #6 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #7 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #8 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #9 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4177 4177 in /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp (gdb) bt #0 HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4177 #1 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=255) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #2 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #3 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #4 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #5 0xb5d8bf5b in kdemain (argc=4, argv=0x859d548) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #6 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #7 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #8 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #9 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 Continuing. ^C Program received signal SIGINT, Interrupt. 0xb5d7c270 in gzeof@plt () from /usr/lib/kde4/kio_http.so Current language: auto; currently asm (gdb) bt #0 0xb5d7c270 in gzeof@plt () from /usr/lib/kde4/kio_http.so #1 0xb5d97ce4 in HTTPProtocol::readBody (this=0xbfd3a000, dataInternal=false) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:4173 #2 0xb5da44b0 in HTTPProtocol::proceedUntilResponseContent (this=0xbfd3a000, dataInternal=80) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:534 #3 0xb5da53a7 in HTTPProtocol::get (this=0xbfd3a000, url=@0xbfd39f2c) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:1214 #4 0xb78776d4 in KIO::SlaveBase::dispatch (this=0xbfd3a008, command=67, data=@0xbfd39fc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1035 #5 0xb7875cfc in KIO::SlaveBase::dispatchLoop (this=0xbfd3a008) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #6 0xb5d8bf5b in kdemain (argc=4, argv=0x859d548) at /build/buildd/kde4libs-4.2.4/kioslave/http/http.cpp:110 #7 0x0804dd11 in launch (argc=4, _name=0x85b4764 "kio_http", args=0x85b47de "", cwd=0x0, envc=0, envs=0x85b47e3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 "0") at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #8 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #9 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #10 0x0804f604 in main (argc=2, argv=0xbfd3a824, envp=0xbfd3a830) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 I forgot to specify the version of yaWP. I'm using the latest version, yaWP 0.2.3. Thanks for all the backtraces. I'm reworking the cace code currently for variuos reasons, and I'm pretty sure that I know what causes the problem (or better, two possible causes) in the old code. Not sure yet if the new code is going to make it into 4.3, but I think so. Hi to all, Ruan made a workaround. It is in YaWP svn now. Could you test it? Thanks I've tried the latest yawp from svn..atm work. Hmm Marian I took svn version, updated, restarted and it does not connect at all I can't even get the cities list... it's connecting and connecting and nothing happens. KDEE 4.2.3 Giueseppe did you restert or log out and log in after update? I use kde 4.2.4 qt 4.5.1,try to delete any old file configuration of yawp i have it ! [dimitris@localhost ~]$ gdb kio_http 4929 GNU gdb 6.8-6mdv2009.1 (Mandriva Linux release 2009.1) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i586-mandriva-linux-gnu"... kio_http: No such file or directory. Attaching to process 4929 Reading symbols from /usr/bin/kdeinit4...Reading symbols from /usr/lib/debug/usr/bin/kdeinit4.debug...done. done. Reading symbols from /usr/lib/libQtCore.so.4...done. Loaded symbols for /usr/lib/libQtCore.so.4 Reading symbols from /lib/i686/libpthread.so.0...done. [Thread debugging using libthread_db enabled] [New Thread 0xb5fea6d0 (LWP 4929)] Loaded symbols for /lib/i686/libpthread.so.0 Reading symbols from /usr/lib/libkdecore.so.5...Reading symbols from /usr/lib/debug/usr/lib/libkdecore.so.5.2.0.debug...done. done. Loaded symbols for /usr/lib/libkdecore.so.5 Reading symbols from /usr/lib/libkparts.so.4...Reading symbols from /usr/lib/debug/usr/lib/libkparts.so.4.2.0.debug...done. done. Loaded symbols for /usr/lib/libkparts.so.4 Reading symbols from /usr/lib/libX11.so.6...done. Loaded symbols for /usr/lib/libX11.so.6 Reading symbols from /usr/lib/libkio.so.5...Reading symbols from /usr/lib/debug/usr/lib/libkio.so.5.2.0.debug...done. done. Loaded symbols for /usr/lib/libkio.so.5 Reading symbols from /usr/lib/libkdeui.so.5...Reading symbols from /usr/lib/debug/usr/lib/libkdeui.so.5.2.0.debug...done. done. Loaded symbols for /usr/lib/libkdeui.so.5 Reading symbols from /usr/lib/libQtGui.so.4...done. Loaded symbols for /usr/lib/libQtGui.so.4 Reading symbols from /usr/lib/libstdc++.so.6...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/i686/libc.so.6...done. Loaded symbols for /lib/i686/libc.so.6 Reading symbols from /lib/libz.so.1...done. Loaded symbols for /lib/libz.so.1 Reading symbols from /usr/lib/libgthread-2.0.so.0...done. Loaded symbols for /usr/lib/libgthread-2.0.so.0 Reading symbols from /lib/i686/librt.so.1...done. Loaded symbols for /lib/i686/librt.so.1 Reading symbols from /usr/lib/libglib-2.0.so.0...done. Loaded symbols for /usr/lib/libglib-2.0.so.0 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/i686/libm.so.6...done. Loaded symbols for /lib/i686/libm.so.6 Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/libQtNetwork.so.4...done. Loaded symbols for /usr/lib/libQtNetwork.so.4 Reading symbols from /usr/lib/libQtDBus.so.4...done. Loaded symbols for /usr/lib/libQtDBus.so.4 Reading symbols from /usr/lib/libbz2.so.1...done. Loaded symbols for /usr/lib/libbz2.so.1 Reading symbols from /usr/lib/liblzma.so.2...done. Loaded symbols for /usr/lib/liblzma.so.2 Reading symbols from /usr/lib/libQtXml.so.4...done. Loaded symbols for /usr/lib/libQtXml.so.4 Reading symbols from /usr/lib/libxcb.so.1...done. Loaded symbols for /usr/lib/libxcb.so.1 Reading symbols from /usr/lib/libstreamanalyzer.so.0...done. Loaded symbols for /usr/lib/libstreamanalyzer.so.0 Reading symbols from /usr/lib/libsolid.so.4...Reading symbols from /usr/lib/debug/usr/lib/libsolid.so.4.2.0.debug...done. done. Loaded symbols for /usr/lib/libsolid.so.4 Reading symbols from /usr/lib/libfam.so.0...done. Loaded symbols for /usr/lib/libfam.so.0 Reading symbols from /lib/libacl.so.1...done. Loaded symbols for /lib/libacl.so.1 Reading symbols from /lib/libattr.so.1...done. Loaded symbols for /lib/libattr.so.1 Reading symbols from /usr/lib/libXrender.so.1...done. Loaded symbols for /usr/lib/libXrender.so.1 Reading symbols from /usr/lib/libQtSvg.so.4...done. Loaded symbols for /usr/lib/libQtSvg.so.4 Reading symbols from /usr/lib/libSM.so.6...done. Loaded symbols for /usr/lib/libSM.so.6 Reading symbols from /usr/lib/libICE.so.6...done. Loaded symbols for /usr/lib/libICE.so.6 Reading symbols from /usr/lib/libXtst.so.6...done. Loaded symbols for /usr/lib/libXtst.so.6 Reading symbols from /usr/lib/libXcursor.so.1...done. Loaded symbols for /usr/lib/libXcursor.so.1 Reading symbols from /usr/lib/libXfixes.so.3...done. Loaded symbols for /usr/lib/libXfixes.so.3 Reading symbols from /usr/lib/libpng12.so.0...done. Loaded symbols for /usr/lib/libpng12.so.0 Reading symbols from /usr/lib/libfreetype.so.6...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libgobject-2.0.so.0...done. Loaded symbols for /usr/lib/libgobject-2.0.so.0 Reading symbols from /usr/lib/libfontconfig.so.1...done. Loaded symbols for /usr/lib/libfontconfig.so.1 Reading symbols from /usr/lib/libXext.so.6...done. Loaded symbols for /usr/lib/libXext.so.6 Reading symbols from /lib/libpcre.so.0...done. Loaded symbols for /lib/libpcre.so.0 Reading symbols from /usr/lib/libXau.so.6...done. Loaded symbols for /usr/lib/libXau.so.6 Reading symbols from /usr/lib/libXdmcp.so.6...done. Loaded symbols for /usr/lib/libXdmcp.so.6 Reading symbols from /usr/lib/libstreams.so.0...done. Loaded symbols for /usr/lib/libstreams.so.0 Reading symbols from /usr/lib/libxml2.so.2...done. Loaded symbols for /usr/lib/libxml2.so.2 Reading symbols from /usr/lib/gconv/UTF-16.so...done. Loaded symbols for /usr/lib/gconv/UTF-16.so Reading symbols from /usr/lib/libkonq.so.5...done. Loaded symbols for /usr/lib/libkonq.so.5 Reading symbols from /usr/lib/kde4/kio_http.so...Reading symbols from /usr/lib/debug/usr/lib/kde4/kio_http.so.debug...done. done. Loaded symbols for /usr/lib/kde4/kio_http.so Reading symbols from /usr/lib/libkntlm.so.4...Reading symbols from /usr/lib/debug/usr/lib/libkntlm.so.4.2.0.debug...done. done. Loaded symbols for /usr/lib/libkntlm.so.4 Reading symbols from /usr/lib/libgssapi_krb5.so.2...done. Loaded symbols for /usr/lib/libgssapi_krb5.so.2 Reading symbols from /usr/lib/libkrb5.so.3...done. Loaded symbols for /usr/lib/libkrb5.so.3 Reading symbols from /usr/lib/libk5crypto.so.3...done. Loaded symbols for /usr/lib/libk5crypto.so.3 Reading symbols from /lib/libcom_err.so.2...done. Loaded symbols for /lib/libcom_err.so.2 Reading symbols from /usr/lib/libkrb5support.so.0...done. Loaded symbols for /usr/lib/libkrb5support.so.0 Reading symbols from /lib/libresolv.so.2...done. Loaded symbols for /lib/libresolv.so.2 Reading symbols from /usr/lib/libssl.so.0.9.8...done. Loaded symbols for /usr/lib/libssl.so.0.9.8 Reading symbols from /usr/lib/libcrypto.so.0.9.8...done. Loaded symbols for /usr/lib/libcrypto.so.0.9.8 Reading symbols from /usr/lib/gconv/ISO8859-7.so...done. Loaded symbols for /usr/lib/gconv/ISO8859-7.so Reading symbols from /lib/libdbus-1.so.3...done. Loaded symbols for /lib/libdbus-1.so.3 0xb67d21ea in gzread () from /lib/libz.so.1 Missing debug package(s), you should install: bzip2-debug-1.0.5-5mdv2009.1.i586 dbus-debug-1.2.4.4permissive-2mdv2009.1.i586 e2fsprogs-debug-1.41.4-1mnb2.i586 fontconfig-debug-2.6.0-5mdv2009.1.i586 freetype2-debug-2.3.9-1mdv2009.1.i586 freetype2-debug-2.3.9-1plf2009.1.i586 gamin-debug-0.1.10-2mdv2009.1.i586 gcc-debug-4.3.2-5mnb2.i586 glib2.0-debug-2.20.1-1mdv2009.1.i586 glibc-debug-2.9-0.20081113.5mnb2.i586 kdebase4-debug-4.2.2-7mdv2009.1.i586 krb5-debug-1.6.3-9mdv2009.1.i586 libice-debug-1.0.5-1mdv2009.1.i586 libpng-debug-1.2.35-1mdv2009.1.i586 libsm-debug-1.1.0-1mdv2009.1.i586 libx11-debug-1.2.1-1.2mdv2009.1.i586libxau-debug-1.0.4-1mdv2009.1.i586 libxcb-debug-1.2-1mdv2009.1.i586 libxcursor-debug-1.1.9-3mdv2009.1.i586 libxdmcp-debug-1.0.2-6mdv2009.1.i586 libxext-debug-1.0.5-2mdv2009.1.i586 libxfixes-debug-4.0.3-4mdv2009.1.i586 libxml2-debug-2.7.3-2mdv2009.1.i586 libxrender-debug-0.9.4-4mdv2009.1.i586 libxtst-debug-1.0.3-3mdv2009.1.i586 openssl-debug-0.9.8k-1.1mdv2009.1.i586 pcre-debug-7.8-3mdv2009.1.i586 qt4-debug-4.5.0-3mdv2009.1.i586 strigi-debug-0.6.4-2mdv2009.1.i586 xz-debug-4.999.8beta-0.2mdv2009.1.i586 zlib-debug-1.2.3-13mdv2009.1.i586 (gdb) Created attachment 34761 [details]
gdb kio_http backtrace
I was using two yawp widgets under Manriva 2009.1 without problems until this week, then suddenly I'm seeing this too. According to rpm -qi I installed yawp on 20th May, so it must be something else that changed recently. Is it possible to give any indication of files I should check for relevant changes during this last few days? It doesn't seem to be yawp itself. @Anne Wilson: Hard to say. Maybe Qt, kdelibs or just some special status of network connection :-( (In reply to comment #49) > Hmm Marian I took svn version, updated, restarted and it does not connect at > all > I can't even get the cities list... it's connecting and connecting and nothing > happens. KDEE 4.2.3 > The same situation on my work box. I think it is caused by proxy. Have to check it. After installing the current yawp version from svn I don't see the problem any more. Now with the current yawp I don't get high CPU usage in kdeini4 any more. But plasma process after a while gets into the state high CPU usage. So this "fix" in yawp isn't good enough. (In reply to comment #57) > Now with the current yawp I don't get high CPU usage in kdeini4 any more. > But plasma process after a while gets into the state high CPU usage. > So this "fix" in yawp isn't good enough. The same situation on my box. Unfortunately my C++ skills are not good enough :-( Yes i confirm,after some time plasma go 100% cpu This should be a duplicate of the recently fixed 175967 based on the backtraces I see. *** This bug has been marked as a duplicate of bug 175967 *** |