Re: GC and dispose

Daniel Billingsley wrote:

As somebody else said, the Dispose pattern is for making sure
UNMANAGED resources inside your classes get cleaned up.

This more clear to me now. I really thought Dispose would help GC.
Thank you and the rest for the clarification.

I have no idea what "several times more memory than equivalent native
applications" means. Equivalent how -Functionality? Code? That's
such a nebulous comparison I don't think I'd spend much time worrying
about that either.

I admit that is based entirely on my experience and not in crystal
clear measurements. My heuristics mechanism takes under consideration
all the factors: Functionality, Number of Forms etc. Sure, I might be
inaccurate in my comparison, but the numbers are very different between
native and managed applications. My native applications take memory and
give it back as soon as I don't need the resources I've used. In
managed applications, the memory keeps being eaten until the GC decides
it is time to collect. The problem with this is that my customer does
run more applications than one. The customer also uses his computer for
other puproses, so she runs third party applications too. So to
conclude, I don't have a specific problem, other than the need to tell
my customers to add some more memory to their machines. Maybe it is not
a leak, it is just taking the GC a long time to collect back the memory.

--
Petros
.

Relevant Pages

  • Re: xmalloc string functions
    ... require memory allocations depending on the way the system works. ... If the toolkit being used is not one of those, then it is irrelevant that some provide a means to do so, particularly if the "some" are not available for the platform being targeted. ... Not enough context for most real-world applications to recover at this point. ... At this point g_malloccalling abortbecomes a moot point, particularly if your auto-save code is robust against memory allocation errors. ...
    (comp.lang.c)
  • Re: ProDOS Plus
    ... operating system was not considered worth the problems when it was just as easy to make the applications support 128k or more ram. ... your suggested P-code system could do something similar by running in the aux 64k memory range $D000...FFFF or perhaps the aux ram used by the P8 /ram driver code space. ... the OS could fit in *only* the space that ProDOS now occupies. ... if practicality were a concern we probably wouldn't be using old hardware. ...
    (comp.sys.apple2)
  • Re: xmalloc string functions
    ... If these were the only choices (crashing applications or a frozen ... trying to malloc some rediculously large amount of memory - e.g. in the ... because their malloc wrapper decided to exit. ... Exiting on malloc failure makes sense for a utility like sort. ...
    (comp.lang.c)
  • Re: xmalloc string functions
    ... require memory allocations depending on the way the system works. ... Not enough context for most real-world applications to ... It is /more/ reliable to routinely auto-save the user's work (as you ... particularly if your auto-save code is robust against memory allocation ...
    (comp.lang.c)
  • RE: DLLHOST.EXE and Secure Server Crash
    ... This is a very common problem with COM+ components and IIS. ... | Applications view switch to Status View) ... |>with 2-3 dedicated SSL servers. ... A symptom of the problem centers around memory ...
    (microsoft.public.inetserver.iis.security)
Loading