Justin, Jon thanks a lot for replying
I do call GC.Collect() on some place, my application is a race software so I
call GC.Collect() after unloading a race or loading a new race. This was in
the old version as well as in the new version. The problem is also that the
software takes a huge amount of memory at startup, and the system runs out
of virtual memory after 15 minutes, with no other programs running.
Jon was saying that I may be using some unspecified behaviour. I believe
that all methods I call from the .NET class library are documented and I use
them as indicated in MSDN. I also checked the breaking changes in version
1.1, and none of them affects my program.
But one of the assemblies in the application is built using a dll generation
tool that I made using System.Reflection.Emit, originally the dll was
generated using .NET version 1.0, but I recompiled my tool with 1.1 and
generated the assembly again to use 1.1
Although it was not my intention to protect the code in the generated
assembly in any way, but all decompilers that I know of can't decompile my
assembly, because I optimise the IL code in a different way than the C#
compiler, yet I still use well documented IL instructions.
Also, the software is working very good on my development machine, with 1GB
RAM, and it runs for days very good. But I need to make it run on 256MB and
128 MB machines, and it did very good with .NET ver 1.0
Sorry for the long problem description.
And Thanks a lot for your help
Best Regards
Sherif
[quoted text, click to view] "Justin Rogers" <Justin@games4dotnet.com> wrote in message
news:#lmNvaibDHA.3520@tk2msftngp13.phx.gbl...
> There are some undiagnosed issues where a machine with a rather large
amount
> of system memory can cause the GC to heuristics to not kick in in time to
> collect and bring the virtual memory back down. I've worked on a number
of
> applications that have had the issue of the GC allowing an application to
> take up nearly all system memory before actually running a collection. Yo
u
> may want to find some opportune places in your code to place GC.Collect(2)
> statements and see if that brings your application back to life.
>
> --
> Justin Rogers
> DigiTec Web Consultants, LLC.
>
> "Jon Skeet" <skeet@pobox.com> wrote in message
> news:MPG.19b90b14beeebdee98a411@news.microsoft.com...
> > Sherif ElMetainy <elmeteny@wayout.net> wrote:
> > > I had a windows forms application that was originally developed using
> .NET
> > > 1.0, it was running fine but lately i decided to move to .NET 1.1
> > > Now the application takes a lot of memory at startup (about 150 MB)
> compared
> > > to 20 MB when running on .NET ver 1.0.
> > > And after running for about 15 minutes the computer runs out of
virtual
> > > memory (Windows 2000 Pro, SP4, 256MB, .NET ver 1.1, all windows
updates
> > > installed) . The code for the application is unchanged between the 2
> > > versions, just recompiled.
> > >
> > > Is there a solution for this, or should I just revert to old good
> version
> > > 1.0? Since for me 1.1 caused problems and less performance.
> >
> > It sounds like maybe you were relying on unspecified behaviour before,
> > and it's changed. Have you been able to write an example program which
> > demonstrates the problem, or used a profiler to try to work out where
> > the heap is being used?
> >
> > --
> > Jon Skeet - <skeet@pobox.com>
> >
http://www.pobox.com/~skeet/
> > If replying to the group, please do not mail me too
>
>
