|
|
 Posted 6/7/2006 8:54:44 AM |
|
|
Forum Member
Group: Forum Members
Last Login: 3/27/2007 2:24:49 PM
Posts: 16,
Visits: 13
|
|
I saw something odd this morning in FeedDemon 2.0.0.23. I'd posted previously about extremely high CPU loads during feed updates. That still occurs, though not as badly as it once did now that I manually clean up older entries, rather than letting FeedDemon do it automatically. But this morning I noticed a high CPU load, and Task Manager showed FeedDemon as the cause. However, FD was not updating. In fact, other than looking in Task Manager, I couldn't see that FD was doing anything. This went on for quite a while. I killed FD, restarted it, and it was fine. But about 15 minutes later, after it had updated, it started doing this again. I notice that I cannot manually initiate an update when this is happening, by the way. Nothing happens when I do an update either on all my feeds, nor on a specific folder. What I can do to pin down what the app is doing?
|
|
|
|
| Posted 6/8/2006 2:41:10 AM |
|
|
Forum Member
Group: Forum Members
Last Login: 9/24/2009 6:38:21 AM
Posts: 27,
Visits: 85
|
|
Same here - I have never seen these high CPU loads before, but upgraded yesterday from build 2.0.0.23 (I think it was) to 2.0.0.24. Heard my laptop chugging away (XP sp2 1gig ram) and found Feeddemon eating 50 CPU. Closed and restarted and no problem - wonder what's up..
Brett
|
|
|
|
| Posted 6/8/2006 4:31:15 AM |
|
|
Forum Member
Group: Forum Members
Last Login: 6/8/2006 4:57:00 PM
Posts: 2,
Visits: 1
|
|
I am seeing 90+% CPU since upgrading to 2.0.0.24.
Because of this I can no longer use FeedDemon. I must revert to 2.0.0.23.
|
|
|
|
| Posted 6/8/2006 7:02:23 AM |
|
|
Forum Member
Group: Forum Members
Last Login: 3/27/2007 2:24:49 PM
Posts: 16,
Visits: 13
|
|
I've always seen high CPU loads in version 2.0 during updates; it's better if you turn off the feature that removes older posts as updates come in. But then you have to regularly do the cleanup wizard manually. However, the load during update alone is still much higher than it should be. I upgraded this morning to the 2.0.0.24, and that appears to have fixed the mystery activity. I may have had a corrupted version of 23. Ooops, nevermind. It's back. High CPU load (around 53 percent) but no apparent updating activity. This time, thought, I am able to force it to update while this is going on. Couldn't make that happen before. I may have to abandon FeedDemon if I can't resolve this. It's not good.
|
|
|
|
| Posted 6/8/2006 9:06:52 AM |
|
|
Forum Member
Group: Forum Members
Last Login: 9/24/2009 6:38:21 AM
Posts: 27,
Visits: 85
|
|
I uninstalled 2.0.0.24 completly, cleaned my registry and reinstalled 2.0.0.22 - I then imported my OPML file and had the same problem, strange as I never had the CPU overload problem with my original 22 build. I also tried updating each channel one at a time, and all worked fine until I got to one channel. The conclusion may be that the problem is related to corruption of the OPML file or a dodgy feed.
I was in the process of reinstalling 24 with the default channels to see if I could confirm this, and of course newsgator is telling me I have installed feeddemon too many times on this account - I HATE newsgator on-line - I am going to look at the competition (nothing compares) before firing off the inevitable email to support.
Brett
|
|
|
|
| Posted 6/8/2006 11:46:13 AM |
|
|
Forum Member
Group: Forum Members
Last Login: 9/24/2009 6:38:21 AM
Posts: 27,
Visits: 85
|
|
Here is the folder causing the problem for me (opml attached). Every time I update only this folder CPU usage never goes below 50%, no problem with any other folder.. I even tried synchronizing just this folder with NGOL but it crashed FD (I am not usually set up for NGOL synchronization, nor do i want to be).
Any ideas appreciated, i suppose i could go through each feed and re-subscribe, see if that does it, but i would hope that FD could catch the problem.
Brett
|
|
|
|
| Posted 6/8/2006 12:34:50 PM |
|
|
NewsGator
Group: Administrators
Last Login: Today @ 5:49:23 AM
Posts: 1,723,
Visits: 41,733
|
|
Thanks for providing that OPML, Brett - I was finally able to reproduce the CPU spike after importing it. I'm not sure yet what's causing the CPU spike, but since I can reproduce the problem, I'm pretty sure it will be fixed soon.
Thanks again,
Nick Bradbury
Nick's Blog
|
|
|
|
| Posted 6/8/2006 12:43:35 PM |
|
|
Forum Member
Group: Forum Members
Last Login: 3/27/2007 2:24:49 PM
Posts: 16,
Visits: 13
|
|
Nick, I'm at work; the mystery spike is only happening on my home machine. I'll send you my OPML when I get home tonight.
|
|
|
|
| Posted 6/8/2006 2:13:26 PM |
|
|
NewsGator
Group: Administrators
Last Login: Today @ 5:49:23 AM
Posts: 1,723,
Visits: 41,733
|
|
Update: OK, I've tracked down the CPU spike to Eric Meyer's feed. After some debugging, I discovered that the spike was happening within WININET.DLL (a Windows library that provides Internet functions).
Long story short: I found this Microsoft Support page which describes the problem. Given that this page is dated 2003, I can't say I'm hopeful that this WININET flaw will be fixed any time soon.
Luckily, there is a simple workaround:
* Close FeedDemon
* Open Internet Explorer
* Go to the Advanced page in IE's "Internet Options"
* Look for the checkbox labeled "Use HTTP 1.1"
* Uncheck it
* If you're using a proxy, also uncheck "Use HTTP 1.1 through proxy connections"
* Click OK to close "Internet Options"
The next time FeedDemon updates this feed, it shouldn't spike the CPU.
Best,
Nick Bradbury
Nick's Blog
|
|
|
|
| Posted 6/8/2006 2:36:42 PM |
|
|
Forum Member
Group: Forum Members
Last Login: 3/27/2007 2:24:49 PM
Posts: 16,
Visits: 13
|
|
Nick, I don't have Eric Meyer's feed in my list (I don't think)... Again, I'll send to you later. But do you know what specifically there is about his feed that triggers the wininet.dll flaw? In other words, is there something I can look for in the feeds I do have? Also, note that my situation may be different. I'm not seeing 100 percent utilization, just 53 percent or so. Also, I note in that MSFT KB article that the issue goes through IE 5. IE 6-7 are not mentioned (but it could be that MS hasn't updated the article). Also, the problem on my end happens on Windows XP MCE 2005, with IE7 Beta 2. I've got IE6 on SP1 on my machine at the office, along with FeedDemon 2.0.0.23, and it doesn't do this here (but my feeds aren't identical on the two machines, either).
|
|