Possible Memory Leak? |
Post Reply 
|
| Author | |
Sean 
Groupie 
Joined: 21 February 2005 Location: United States Status: Offline Points: 81 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: Possible Memory Leak?Posted: 23 July 2003 at 11:45am |
|
Program Info: |
|
 |
|
|
LogSat
Admin Group 
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 23 July 2003 at 10:08pm |
|
Sean, Depending on the amount of email traffic, SpamFilter should normally only use about 30-80MB or RAM. The only case were we saw huge amounts of memory used have been when the quarantined items are displayed in the quarantine list. We have had at least two reports were users have seen the quarantine tab become populated with data even after they clicked on the "Hide List" button. Can you please confirm that the quarantine tab indeed does not show any data when the memory runs that high? If the list is empty then we need to look elsewhere. What kind of email activity is going thru SpamFilter (emails/day or emails/hour, average number of concurrent incoming connections at any second)? If you'd like to, we can remote in the server to see if we see anything unusual. Roberto Franceschetti |
|
|
|
|
Sean
Groupie
Joined: 21 February 2005 Location: United States Status: Offline Points: 81 |
Post Options
Thanks(0)
Quote Reply
Posted: 24 July 2003 at 12:22pm |
|
Roberto, I can ensure you the quarentine list is not repopulating during the huge memory usage. I will send the screen shot by email. As for the number of emails per hours: 240 connections average. I will be attempting to remove Spamfilter then reinstall this evening in attempts to correct the problem. |
|
|
|
|
Michael Magill
Guest Group 
|
Post Options
Thanks(0)
Quote Reply
Posted: 25 July 2003 at 11:19am |
|
We have had the same memory leak issue. We run spamfilter as a service and have found that it does not leak memory if the server's console is not logged on. It appears to be a GUI memory leak.You can logon to use the SpamFilter GUI, just log back off so there is little or no memory leakage. Also you can use terminal services or network shares to edit the spamfilter text files manually. These files are reloaded by spamfilter every few minutes, or you can restart the spamfilter service to force an immediate reload. You can not use the GUI via Terminal services or LAN shares, though. It is console bound. We (along with others) have been rallying for a serperation of GUI and service, but so far to no avail.This workaround works well for us.
|
|
|
|
|
Sean
Groupie
Joined: 21 February 2005 Location: United States Status: Offline Points: 81 |
Post Options
Thanks(0)
Quote Reply
Posted: 29 July 2003 at 3:17pm |
|
I did a reinstall, with no luck to correcting this problem. As well as loggin off the consol as Micheal suggested, still no luck. I plan on installing the new build here shortly, maybe it will fix it?
|
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 29 July 2003 at 3:31pm |
|
Sean, The new build should not have anything new to fix the memory leak as we're not able to repoduce the problem. Again, if you'd like to, we can remote in the server to see if we see anything unusual. Roberto F. |
|
|
|
|
Meister
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 30 July 2003 at 1:11pm |
|
I have the same problem.
I looked, when the problem occured, in the "connection" screen only one connection from one sender, and the status is "RCPT TO". And the SpamFilter server getting start use the memory. From 12MB to 170MB, and I shut down the process. How can I set, tha one mail maximal size? (I use your unlicensed eval software, 1.2.0.178).
Meister |
|
|
|
|
Meister
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 30 July 2003 at 2:10pm |
|
When the problem occure, the SpamFilter use not only 7 threads, it use 8 threads. And slowly eat the memory, with 100% processor. (And it's not a wrong processor to handle only one mail one time.. :-)
On the quaranten sceeen is not any mail. Currently use 450MB of memory. |
|
|
|
|
Meister
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 30 July 2003 at 2:33pm |
|
Here is the source of the message, that halt my server: Return-Path: <hirlap@komarominyomda.hu> ------=_20030730202719_99208 -------- Eredeti üzenet -------- Your message Címzett: knyomda@axelero.hu Was displayed on Tue, July 29, 2003 6:30 pm
------=_20030730202719_99208 Reporting-UA : linux.komarominyomda.hu ; SquirrelMail (version 1.2.7) ------=_20030730202719_99208--
|
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 30 July 2003 at 6:16pm |
|
Meister, Can you please email us at support@logsat.com the full source of this email? Roberto F. |
|
|
|
|
Meister
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 30 July 2003 at 6:55pm |
|
Sorry.
The sender server isn't my server.
I think, the sender resend the message, and I enable the debug view. Here is the log:>>EHLO linux.komarominyomda.hu
>EHLO linux.komarominyomda.hu
>EHLO linux.komarominyomda.hu
EHLO linux.komarominyomda.hu
EHLO linux.komarominyomda.hu
<<250-AUTH LOGIN
<<250-8BITMIME
<<250 HELP
>>MAIL FROM:MAIL FROM:MAIL FROM:
|
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 31 July 2003 at 1:11am |
|
In the registered are we just uploaded beta build .192. Could you please try this latest version to see if it fixes the memory leak issue? Roberto |
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 31 July 2003 at 1:13am |
|
Sean, In the registered are we just uploaded beta build .192. Could you please try this latest version to see if it fixes the memory leak issue? We did find that sometimes the quarantine grid repopulated by itself, consuming large quantities of RAM is the quarantine DB is fairly big, and this build should have fixed that. Roberto |
|
|
|
|
Meister
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 31 July 2003 at 4:07am |
|
Ok, I will try it, if I have a copy from it.
I use the unlicensed eval copy.
But I think, the problem not with the Quaranten-grid, because when sent this prblematics e-mail from this probl. server, the connection live one hour, and I cannot kill this.I think, thge problem in the SMTP implementattion.
(I don't know, this bug is the SpamFilter, or the another server, but the problem occured on my server with your sodftware.)
|
|
|
|
|
Meister
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 31 July 2003 at 6:58am |
|
I think, this problem not in the gui.
I created a rule to bypass all letter to this recipient, and the log is the next: 07.31.03 12:39:59:290 -- (3720) Connection from: 195.228.227.14 - Originating country : Hungary The from server is same as that I wrote in the previous posts. I think, this server not send "normal" letter, but it shoudn't been an explaination.
|
|
|
|
|
Sean
Groupie
Joined: 21 February 2005 Location: United States Status: Offline Points: 81 |
Post Options
Thanks(0)
Quote Reply
Posted: 31 July 2003 at 11:07am |
|
Roberto, I installed the beta version and will test today. |
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 31 July 2003 at 9:53pm |
|
We were able to replicate a similar issue with this email source, and will now work to isolate the problem and patch it. Roberto F. |
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 August 2003 at 2:37am |
|
We found the problem caused by this message and have posted a temporary beta patch (build 1.2.0.194) in the registered user's area. Roberto F. |
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 August 2003 at 2:39am |
|
Sean, We found the problem caused by a specific message posted by Meister on this topic. A very specific malformed subject header was causing a slow but steady memory leak and high CPU. We have posted a temporary beta patch (build 1.2.0.194) in the registered user's area. Roberto F. |
|
|
|
|
Sean
Groupie
Joined: 21 February 2005 Location: United States Status: Offline Points: 81 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 August 2003 at 1:05pm |
|
After installing the first beta you suggeted, "1.2.0.192beta" our memory usage droped significatly (now only using around 75,000K) this was overnight, which before was using over 450,000K. So the change between v1.2.0.190 and 1.2.0.192beta, seemed to slow the leak (Thank You). However as you suggest, I will install the new beta 1.2.0.194 today and see if it helps even more. Thank you again! and Keep up the awesome work. Sean |
|
|
|
|
Meister
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 02 August 2003 at 12:24pm |
|
Dear LogSat!Can I get an URL to download the new version?
I tested it, I took 10 hours to locate the bug in your program.
|
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 03 August 2003 at 12:36am |
|
Answered this by private email...! Roberto |
|
|
|
|
Sean
Groupie
Joined: 21 February 2005 Location: United States Status: Offline Points: 81 |
Post Options
Thanks(0)
Quote Reply
Posted: 14 August 2003 at 8:35am |
|
If you are experiencing this problem as well, PLEASE REFER TO THE TOPIC BELOW: http://www.logsat.com/spamfilter/forums/showmessage.asp?messageID=1655
|
|
|
|
Topic Options|
Post Reply
|
|
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.361 seconds.