Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Friday, November 22, 2024 
 
slxdeveloper.com Community Forums  
   
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
 Off Topic Forums - General & Off Topic
Forum for off topic and general discussion. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to General & Off Topic | New ThreadView:  Search:  
 Author  Thread: SLX Memory Leaks
Yup.
Posts: 126
 
SLX Memory LeaksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 04 Apr 08 3:52 PM
There may be an obvious answer here, but is SLX notorious for memory leaks? If I do not restart our SQL Server every month, fields will stick in certain places and whatnot. Would my best course of action, besides restarting the server more often, be to see when these memory leaks occur and then start going through the code that I can see? I would image that the memory leaks are due to poor coding of plug ins, but I've been wrong before.

SLX 6.2.6/Win2k3 Server/MS SL Server 2000
[Reply][Quote]
John H. Hedges
Posts: 62
 
Re: SLX Memory LeaksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 05 Apr 08 12:26 AM
SLX 6.2.6 isn't notorious for memory leaks - if anything, it's the most stable version they've ever released. SLX 4.x was a little dodgy in that area, and SLXweb versions up through 6.1 had a few resource-related problems on the server, though even there I wouldn't use the word "notorious"...

Given that the term "memory leak" usually refers to a process that isn't releasing memory sectors and/or file handles, the thing to do is get yourself some good monitoring utilities and see what's really going on. Microsoft recently bought Sysinternals, and all of those are pretty good, as well as free (for now, anyway)... If it really is SQL Server that's failing to release memory/handles, you might be able to see if SLX is really the culprit by looking at unreleased SPID's in Enterprise Manager to see what application (or DB user account) owns them.

You might also consider upgrading to SQL 2005 if you can - not so much because it manages resources that much better, but because the monitoring and management features are a distinct improvement.

Last but not least, what else can you tell us about your setup? Are you running both SLXweb and the LAN client? Are any of the SLX server apps running on the same box as MSSQL? If you've got sync going, how many users on the sync server(s)? Is ExchangeLink involved? If you're running SLXweb, are you also running the Reports server? You know, stuff like that.
[Reply][Quote]
Mike Spragg
Posts: 1226
Top 10 forum poster: 1226 posts
 
Re: SLX Memory LeaksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 05 Apr 08 1:58 AM
It's highly unusual to have to do this - SQL Server is dependent on using lots of memory (or perform well) so rebooting just kills the cache. I would suspect something else - but not knowing the environment I can't really comment. What do yo mean by "stick" ? What's happening during those events ?
[Reply][Quote]
Bob (RJ)Ledger
Posts: 1103
Top 10 forum poster: 1103 posts
 
Re: SLX Memory LeaksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 05 Apr 08 10:15 AM
The typical thing that causes memory leaks is bad coding/design..

ALWAYS remember to close recordsets and set objects to Nothing ..

EX:
Dim objRS00
...
Set objRS00 = ......
objRS00.Open
..
objRS00.Close
..
Set objRS00 = Nothing
--
RJLedger - rjlSystems
[Reply][Quote]
Yup.
Posts: 126
 
Re: SLX Memory LeaksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 07 Apr 08 7:54 AM
Our setup consists of just LAN clients. We do not run sync server, I guess you could say our setup is fairly basic. My assumption is that this is due to poor coding in customizations. Unfortunately I will not be able to look into this further until I free up some time. Any recommended utilities to look into from Sysinternals?

Mike-
When I saying something sticks in SLX, an example would be the ship to company name on a printed report shows as the same name for every sales order. The address information will change based on the sales order, but the company name will not.

RJ-
Unfortunately 95% of the customizations made to SLX were performed prior to my employment with my current company. Nonetheless, it appears I will have to perform some monitoring as John had suggested, and then proceed to going through plug-ins we use, starting with the most frequently used.
[Reply][Quote]
John H. Hedges
Posts: 62
 
Re: SLX Memory LeaksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 07 Apr 08 12:07 PM
Of the SysInternals utilities, the first thing to try is Process Explorer, which shows you pretty much everything, nicely color-coded (go to View|Columns to choose what you want to look at - a good one is "Private Bytes" on the Process Memory tab). Then you'll have to run through various SLX tasks and see which ones cause the amount of memory-in-use to rise, and not fall when you're finished with them. Process Monitor and Registry Monitor are also useful once you discover which programs are causing you the most trouble, and DebugView is of course indispensible for most SLX programming... Also, the AutoRuns program is the best (and most exhaustive) way I know of to keep track of startup programs, and TDImon is good for finding botnet zombies and things like that.

However, if you're just using the LAN client and no sync, particularly with that version of SLX, it probably *is* a failure to close table handles in script/form plugins. And unfortunately, when you find one of those in a plugin, you'll usually find more of them in other plugins too, because it's often due to a bad coding habit rather than a single oversight. (Sorry...!)
[Reply][Quote]
Jeremy Brayton
Posts: 491
Top 10 forum poster: 491 posts
 
Re: SLX Memory LeaksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 08 Apr 08 2:20 AM
Oooh ooh I know this one!

SQL never "releases" memory. You start the process and it climbs and climbs until it hits the dynamic cealing. Is it harmful? Not really, it's kind of like Vista's precache feature except it doesn't truly "let go" of RAM unless the OS needs it. Most of the time the OS doesn't need it so that number will stay high after a prolonged uptime. I used google to research this phenomenon and everything pointed to it being standard procedure. If we're talking about specifically the sqlsvr process or whatever it's really named.

If you see SLX services grab memory and not let go then you need to start looking into memory leaks or, depending on the service, configuration errors (and shoddy coding).
[Reply][Quote]
Yup.
Posts: 126
 
Re: SLX Memory LeaksYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 21 May 08 2:28 PM
I have been watching SLX memory usage, and just as an example, some users memory usage will climb to about 500MB. It will all later be released when SLX freezes.
[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 11/22/2024 8:55:34 PM