Results 1 to 8 of 8

Thread: NotifyIcon

  1. #1

    Thread Starter
    KrisSiegel.com Kasracer's Avatar
    Join Date
    Jul 2003
    Location
    USA, Maryland
    Posts
    4,985

    NotifyIcon

    Why the hell does it use so much ram for a tiny ass picture!?

    When working on an example of a context menu and NotifyIcon made with only code, either language I used (C# or VB) it ALWAYS took up about 17MB of ram.

    When I add it to any of my projects it seems to add about 10-11MB of ram usage. That's just physical usage, I wasn't even monitoring the VM usage.

    Why the hell? Does the framework have a memory leak somewhere?

  2. #2
    Sleep mode
    Join Date
    Aug 2002
    Location
    RUH
    Posts
    8,083
    Originally posted by kasracer
    When working on an example of a context menu and NotifyIcon made with only code, either language I used (C# or VB) it ALWAYS took up about 17MB of ram.
    only code ? this code creates objects in memory . I mean we don't measure what these lines consume of memory . So , when you declare an instance of Context menu , it may take some big allocation on the heap plus the icons if you added some .

  3. #3

    Thread Starter
    KrisSiegel.com Kasracer's Avatar
    Join Date
    Jul 2003
    Location
    USA, Maryland
    Posts
    4,985
    Originally posted by Pirate
    only code ? this code creates objects in memory . I mean we don't measure what these lines consume of memory . So , when you declare an instance of Context menu , it may take some big allocation on the heap plus the icons if you added some .
    It shouldn't need to allocate 11MB for an icon. It's usually a bit more with the context menu.

  4. #4
    Sleep mode
    Join Date
    Aug 2002
    Location
    RUH
    Posts
    8,083
    Originally posted by kasracer
    It shouldn't need to allocate 11MB for an icon. It's usually a bit more with the context menu.
    Ok , this happens the first time you run it but after couple of times of running the same app , this number should be decreased to 60% at least , did you notice this ?

  5. #5

    Thread Starter
    KrisSiegel.com Kasracer's Avatar
    Join Date
    Jul 2003
    Location
    USA, Maryland
    Posts
    4,985
    Originally posted by Pirate
    Ok , this happens the first time you run it but after couple of times of running the same app , this number should be decreased to 60% at least , did you notice this ?
    No it was always the same and it shouldn't decrease just by running it a couple of times, it should remain constant.

  6. #6
    Sleep mode
    Join Date
    Aug 2002
    Location
    RUH
    Posts
    8,083
    My computer does consume less after running the same app multiple times . Try it yourself .Anyways , we'd discussed this before in a long thread in VB.NET Forum , maybe you can get something useful if you look it up .

  7. #7

    Thread Starter
    KrisSiegel.com Kasracer's Avatar
    Join Date
    Jul 2003
    Location
    USA, Maryland
    Posts
    4,985
    Originally posted by Pirate
    My computer does consume less after running the same app multiple times .
    It's always the same here
    Originally posted by Pirate
    Anyways , we'd discussed this before in a long thread in VB.NET Forum
    No we didn't. You're thinking of compiling, since a .NET application is compiled every execution and is partially cached (parts are still compiled each time). The memory an icon uses should be the same each time.
    Originally posted by Pirate
    maybe you can get something useful if you look it up .
    Look it up where? The MSDN is one large cluster**** with jack crap about this.

  8. #8
    Sleep mode
    Join Date
    Aug 2002
    Location
    RUH
    Posts
    8,083
    Originally posted by kasracer
    Why the hell? Does the framework have a memory leak somewhere?
    JIT Compiler is one of the reasons . I've just found out .

Posting Permissions

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



Click Here to Expand Forum to Full Width