SitePoint Sponsor

User Tag List

Results 1 to 3 of 3

Thread: Memory Leak?!

  1. #1
    SitePoint Wizard silver trophy Jeremy W.'s Avatar
    Join Date
    Jun 2001
    Location
    Toronto, Canada
    Posts
    9,123
    Mentioned
    2 Post(s)
    Tagged
    0 Thread(s)

    Memory Leak?!

    ACH!!!

    Okay, breathe... breathe... bre.... ergh

    Aright, time to explain. We've written a conference registration system. We've written COM's for it. We've called and used those COM's to death. We just did a large user testing session (50 users, 3 hours) and a lot of info came out of it (around 100 suggestions, which we've fixed all of them now)...

    Now, there's a wee little file called DLLHOST.EXE which apparently is the one that calls DLL's, etc. Anyways, each time a user uses the system this adds 5MB of RAM to it's "grab". Each new user adds another 5MB. If you restart a registration it's another 5MB...

    It never let's this RAM allocation go... This is not good.

    Granted, this could be an IIS5 thing (the deployment server will be IIS4) so it may not be a cause for concern, but we really don't want this to go live if we're going to have to restart it every... 5 seconds.
    SVP Marketing, SoCast SRM
    Personal blog: Strategerize
    Twitter: @jeremywright

  2. #2
    SitePoint Zealot
    Join Date
    Oct 2001
    Location
    Dallas/Ft. Worth
    Posts
    101
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    re:

    I'm little confused...you will be running your app on IIS4 and you are testing it on IIS5? Well, to be blunt, who ever made that decision, better be having a really good reason because it just doesn't make sense to do that. It would make sense if your app is going to be in production on IIS5 so you're doing preliminary (component) testing on IIS4 - although even that is pusing it.

    So, first, do yourself a favor and install IIS4 and test it against this server, otherwise, you're mostly wasting your time.

    And as far as your issue with memory, you'll find that whenever you use COM's. Microsoft really didn't pay too much attention to the memory management, although they are getting better. Hopefully, your problem will be solved once you test with IIS4.

    Lastly, what about your code and COM configuration? Perhaps, there is need to do some code reviews and identify potential problems...or you've already done this and didn't find anything.

    Good Luck!

  3. #3
    SitePoint Wizard silver trophy Jeremy W.'s Avatar
    Join Date
    Jun 2001
    Location
    Toronto, Canada
    Posts
    9,123
    Mentioned
    2 Post(s)
    Tagged
    0 Thread(s)
    Update then?

    We fixed it
    SVP Marketing, SoCast SRM
    Personal blog: Strategerize
    Twitter: @jeremywright


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •