Created attachment 950734 [details] strace -s4096 -p `pidof glib-pacrunner` Description of problem: When I enable automatic proxy discovery in Gnome Settings glib-pacrunner starts and eats one of my CPU cores (80-90% per top), which causes battery drain and fans to be turn on at a high speed. Version-Release number of selected component (if applicable): glib-networking-2.38.2-1.fc20.x86_64 How reproducible: Easily Steps to Reproduce: 1. Open Gnome Settings 2. Choose "Network" 3. Choose "Network proxy" 4. Switch method to "Automatic", leave "Configuration URL" empty Actual results: Per top, glib-pacrunner consumes 80-90% of CPU core until killed. Expected results: I don't expect any task to consume so much CPU for a long time (more than few seconds). Additional info: Fresh Fedora 20 with all updates installed. My office network won't work without correct WPAD support.
Created attachment 950735 [details] lsof -p `pidof glib-pacrunner`
The strace shows the main thread being repeatedly woken up by another thread, but there's no hint of why. Can you please do strace -s4096 -f -tt `pidof glib-pacrunner` to get all threads? Thanks.
Created attachment 951159 [details] strace -s4096 -f -tt -p `pidof glib-pacrunner`
So the log shows that in the span of 5 seconds, glib-pacrunner received 523 requests to resolve the proxy for outlook.office365.com:443 (and only managed to reply to 60 of them). Is some other process also using lots of CPU? (Presumably something evolution or gnome-online-accounts related.)
I haven't seen any other process which used lots of CPU. Actually it should be evolution, who tried to resolve office365.com. Does the behavior mean that it is an evolution bug? Or should pacrunner be able to tolerate the load rejecting/caching some requests? I was able to reproduce high CPU usage on another Fedora 20 system.
Created attachment 951522 [details] strace of glib-pacrunner at another system (kelly)
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.