-
🔑 If you are looking for your serial number / activation key code ⟶ Serial Recovery.
📺 If you are looking for documentation or videos ⟶ Have a look at the Tutorial Videos / Frequently Asked Questions / Knowledge Base.
🎟️ You can also contact us privately (please be patient) ⟶ Contact Customer Service.
Bounce Handler Uses Memory Out of Control
- Thread starter dpdexter
- Start date
Hi there,
even if the topic is a bit old.
We do have the same problem. Our workaround is to delete the protocol regularly. I mean the protocol which is beeing produced while the bounce handler checks the inbox. Seems to me that he writes all the protocol down in the memory. Because, after deleting the protocol there is no further problem with the memory.
Would be great to have a option where you can deactivate it.... I see that our version is a bit old. I'll install the new version and see if the problem exists further more...
Greetings!
even if the topic is a bit old.
We do have the same problem. Our workaround is to delete the protocol regularly. I mean the protocol which is beeing produced while the bounce handler checks the inbox. Seems to me that he writes all the protocol down in the memory. Because, after deleting the protocol there is no further problem with the memory.
Would be great to have a option where you can deactivate it.... I see that our version is a bit old. I'll install the new version and see if the problem exists further more...
Greetings!
Hi there!
The problem is still the same.
The BounceHandler is still writing the log into the memory. At least that is what it seems to me.
Isn't it possible to introduce an option which block the writing of the logfile? I do not really use the log quite often and so I could just check the option not to log it during daily business.
Kind regards!
The problem is still the same.
The BounceHandler is still writing the log into the memory. At least that is what it seems to me.
Isn't it possible to introduce an option which block the writing of the logfile? I do not really use the log quite often and so I could just check the option not to log it during daily business.
Kind regards!
same mem problem here, crashes everytime
on very big numbers of emails to grab from a mail account it eventually runs out of memory and crashes. Everytime. I know the log is there BUT I have many different mail accounts/Bouncehandler files yet there is only one log so no way for me to segment which list the entries belong to for me to recover. So basically for me there is no way to recover any downloaded bounces since the last file save if it crashes.
on very big numbers of emails to grab from a mail account it eventually runs out of memory and crashes. Everytime. I know the log is there BUT I have many different mail accounts/Bouncehandler files yet there is only one log so no way for me to segment which list the entries belong to for me to recover. So basically for me there is no way to recover any downloaded bounces since the last file save if it crashes.
BUT, if you have multiple Bouncehandler files tracking for different mail domains/accounts, I can't see where it is possible to recover from your suggested logfile because that is from everything it bounced that day (not separated by Bouncehandler file. If I've got 4 files that have been retrieving bounces during the day but one of them crashes, the recovery you suggest would add emails to the crashed file that were not part of the bulk mail delivery.