Esumsoft Forums

Hi-

Ever since I went from 5.6.2 to 5.6.3 there's been a small but noticeable increase in the time it takes to open a message after double-clicking it in the message list.

I haven't changed any of my existing options re retrieval, viewing, etc. The lag is on all accounts, both gmail and non-gmail.

Wondering if anyone else has observed this.

Thanks in advance,
Efrem

I can't personally say if that's the case or not as I'm no longer using v5, but the code changes between v5.6.2->.3 wouldn't have made this difference.

Is it possible that PP is having to retrieve the message from the server? ie. does the view-message window appear immediately but it takes longer before the message body is displayed (and you might see something like "retrieving message" on the bottom-left of the window).

If that's not what you're seeing and it actually takes longer before the view-message window actually appears -- have you tried rebooting your computer (make sure you install any updates as pending updates will sometimes cause issues like this).

Thanks for the reply, Jeff.

It turns out that the cause was completely unrelated to POP Peeper. I should have updated this thread; sorry.

FWIW, because I had not updated PPv5.6 on my Desktop (Win7) platform for some time - I was provided a unique opportunity to be able to directly compare the two (PPv5.6 and PPv5.6.3) versions over a period of a few days for each of the two PP builds.

Based on my observation (as expected), I can most assuredly say that I did not in any way detect any discernible decrease in performance at all (i.e. lag time) specific to opening messages as compared between PPv5.6 and PPv5.6.3.

efremk1 wrote: ↑Wed May 28, 2025 6:21 am ... It turns out that the cause was completely unrelated to POP Peeper...

Would you feel comfortable sharing with us the "cause" of the delay opening messages (in the event this situation might at some point happen to apply to anyone else)?

I think it was a severe memory leak from a misbehaving beta. The short answer is I saw it on only 1 pc, and it stopped after I killed the offending process.