[quote user="Auser"]The message in the lower left corner has " Applying Filtering Rules....", and there may not have been any new messages.[/quote]

What about turning off filtering for a try? Does your AV scanner scan the new mail directory (every new mail is stored in a single file as opposed to other folders where all messges are stored in a single file only)? If so try without it.

I was using 4.5? on XP and doing well. I upgraded to 4.61 and now win-pm32 pegs at 100% anytime I perform a function. The performance has been terrible.  Is this common? Can I go back to 4.52, if needed? I searched the forums to see if there was something similar, but after searching for 30mins I decided to start my on thread. Help, it takes 5mins to print pmail attachment.

[quote user="Auser"]I was using 4.5? on XP and doing well. I upgraded to 4.61 and now win-pm32 pegs at 100% anytime I perform a function.[/quote]

Go to Tools => Options => Advanced settings and set Load Windows Internet Services ... to Always, then restart Pegasus Mail.

Thanks for the reply. I saw that in another thread and tried it before I made this post. There was no change.

Does "hitting 100%"  mean resource usage ?

Is that reported via Windows System Monitor ?

How many old messages do you have ?

Not sure if I have the right idea, but similar things happened to me before.

Right after I upgraded to 4.62 my system went shot. I used the Task Manager to see if I could find anything and win-pm32 was at 99% and would stay there for some time. Eventually, it would process. I closed all my other apps to see how much of the resource it would use, and whatever was available would be used. Even if I print an email the CPU Usage would hit 100% with win-pm32 at 99%.

Okay, my #1 suspicion is that he's spinning the disk like crazy, "compressing" old folders.

The way I "solved" the problem was to let him spin all day and all night long. I think he needed 6 or 7 hours to get it done.

I know that's not much of a solution for now (anybody else got a better one ?) but that's the only thing I could conjure up when it was happening to me.

**AFTER** that is done, then you can go look at this thread...

http://community.pmail.com/forums/thread/28088.aspx

...and get an idea of how to stop that in the future.

The brass tacks are: you take more disk space, but you don't have to experience this at random times.

Thanks! I left it up over night then rebooted the machine. It seems to be much faster. My printing is very slow, but I am not sure that is a pmail issue. When forwarding with attachments wim-pm32 pegged 99%, but for short periods. I can live with that for a little while.

 Thanks for your help! I will start a new thread if I have other issues.

 Thanks again and have a Blessed Day!

Now it's my turn.  Pegasus has been spinning the disk on my main machine for more than 16 hours now. (Correct: "Sixteen" hours)

Windows Task manager reports that Pegasus (WinPM32,EXE,  I think) is using only 2-to-5 percent of the CPU itself, (and sometimes zero) but is occupying an enormous chunk of RAM, I'm guessing eighty percent of the physical stuff on the motherboard.

It's a one-Gig machine and WinPM32.EXE is frequently taking 800,000K+ bytes of RAM.

[quote user="A01"]It's a one-Gig machine and WinPM32.EXE is frequently taking 800,000K+ bytes of RAM.[/quote]

What about AV scanners interfering?

Never thunk it.  AVG is on that machine.  That does it ?

[quote user="A01"]Never thunk it.  AVG is on that machine.  That does it ?[/quote]

Prove me wrong!

[quote user="idw"]

[quote user="Auser"]I was using 4.5? on XP and doing well. I upgraded to 4.61 and now win-pm32 pegs at 100% anytime I perform a function.[/quote]

Go to Tools => Options => Advanced settings and set Load Windows Internet Services ... to Always, then restart Pegasus Mail.[/quote]

I had the same problem 4.61 upgrade from 4.5x with XP OS too!  The Pmail program would peg 99% CPU and stay there until while the mail downloaded.  If I put it "OFFLINE", it would get worse - it would peg the rail and just stay there until I put it "on-line" and waited until it downloaded.

Your suggestion changed that to about 5% CPU usage.  THANKS!

( As much as I want to just accept this fix and move on, it's got me extremely curious as to how such a simple setting can hose my machine up so majorly.)

Long time Pegasus mail user here, desperate for help: I have the same problem (100% cpu usage) after upgrading to 4.61.

I have seen the suggestions about Load Windows Internet Services, but ---  the program sits in the 100% cpu loop before it ever gets to the interface that will allow me to change that setting.

I've tried letting it run for ~2 hours, but that doesn't seem to have accomplished anything. Tried rolling back to 4.51, but that didn't change anything. Tried starting it up with no internet connection, in case it was waiting from something from the net, but that didn't help.

So: is there some file I can edit to accomplish the  Options setting noted above, as I can't get to the interface to make the change?

Please help; I've got vast amounts of mail files and Pegasus to date has been wonderful in helping cope.

thanks in advance for any assistance.

Reply to my own post. Turns out that a message I sent was undeliverable due to size (80MB), and Pegasus seemed to be choking on this (RVEPN7DZ.CNM) at the "Opening new mail folder" stage. I deleted the file and all is well again.

[quote user="Coach"]( As much as I want to just accept this fix and move on, it's got me extremely curious as to how such a simple setting can hose my machine up so majorly.)[/quote]

You really want to know all the details? Ok, here we go, trying my best: For historical reasons (which I cannot verify myself) Pegasus Mail resorted to loading the Windows WINSOCK library (whatever it's actual name was/is) on demand since this was (supposedly) required for initiating an automated dial-up (and enabled people for using custom SOCKETS implementations). As this became less important since most people nowadays use permanent connections and Pegasus Mail's functionality got more and more extended (using additonal modules such as HTML renderers, but it would also affect any module using HTML help (like my encryption extensions)) another issue became obvious as being

related

to unloading the WINSOCK library: There appear to be implicit dependencies on the WINSOCK library being kept loaded applying to other modules such as the WININET library which in turn is used by almost any module trying to (potentially) download stuff from the Internet (such as HTML renderers or the HTML help system). This wouldn't be an issue, though, if the instance counting supposedly applied to calls to the LoadLibrary() and FreeLibrary() functions would work properly which should prevent function pointers from getting invalidated by unloading the WINSOCK library while other modules still seem to depend on it. The only suprising thing here is that this failure doesn't cause plain crashes instead of high CPU load which would be the more usual result of such issues ...

[quote user="idw"]

[quote user="Coach"]( As much as I want to just accept this fix and move on, it's got me extremely curious as to how such a simple setting can hose my machine up so majorly.)[/quote]

You really want to know all the details? Ok, here we go, trying my best: For historical reasons (which I cannot verify myself) Pegasus Mail resorted to loading the Windows WINSOCK library (whatever it's actual name was/is) on demand since this was (supposedly) required for initiating an automated dial-up (and enabled people for using custom SOCKETS implementations). As this became less important since most people nowadays use permanent connections and Pegasus Mail's functionality got more and more extended (using additonal modules such as HTML renderers, but it would also affect any module using HTML help (like my encryption extensions)) another issue became obvious as being related to unloading the WINSOCK library: There appear to be implicit dependencies on the WINSOCK library being kept loaded applying to other modules such as the WININET library which in turn is used by almost any module trying to (potentially) download stuff from the Internet (such as HTML renderers or the HTML help system). This wouldn't be an issue, though, if the instance counting supposedly applied to calls to the LoadLibrary() and FreeLibrary() functions would work properly which should prevent function pointers from getting invalidated by unloading the WINSOCK library while other modules still seem to depend on it. The only suprising thing here is that this failure doesn't cause plain crashes instead of high CPU load which would be the more usual result of such issues ...[/quote]

It scares me that I actually understand all this.  Thanks!

[quote user="Coach"]It scares me that I actually understand all this.  Thanks![/quote]

I take this as a compliment ... [;)]

Hello,

Since I am having this kind of problem CPU hitting 100% without AV sw active,  I just read the messages posted here and I do not see that there is a solution to this issue.

Is this correct?

Thank you 

Ezio

> Since I am having this kind of problem CPU hitting 100% without AV sw
> active,  I just read the messages posted here and I do see that there
> is a solution to this issue.
>
> Is this correct?

Yes it is, have you followed the instructions to set the Winsock to load always.