Prev: Assembly missing in GAC after Publish?
Next: trying out UDP socket, and failing.... (on Vista)
From: P Chase on 17 Jun 2008 06:45
I am developing an application using Visual Studio 2005, Windows XP
(or 2003) and C#. I am using facilities of .Net Framework 3.0, but not
of 3.5.

I am falling foul of some memory leaks in the framework, which
Microsoft claim to have fixed in .Net Framework 3.5 SP1.

I confess to not really understanding how the various versions of .Net
Framework that have been installed on my machines are actually used by
the application.

So my question is: if the leaks really are fixed in 3.5 SP1, will
installing that service pack also fix the same leaks in 3.0?

(Of course, only the Beta of 3.5 SP1 is currently available, but I
could be brave and try it).
From: "Alvin Bruney [ASP.NET MVP]" vapor dan using hot male spam on 17 Jun 2008 08:00
what memory leak are you seeing? You need to describe it better and give
some more details.

--

Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book, 2nd Edition
Exclusively on www.lulu.com/owc $19.99
-------------------------------------------------------


"P Chase" <peter.chase(a)globalgraphics.com> wrote in message
news:9f5a9847-26a7-4c2d-802e-a4b826b619f7(a)t54g2000hsg.googlegroups.com...
> I am developing an application using Visual Studio 2005, Windows XP
> (or 2003) and C#. I am using facilities of .Net Framework 3.0, but not
> of 3.5.
>
> I am falling foul of some memory leaks in the framework, which
> Microsoft claim to have fixed in .Net Framework 3.5 SP1.
>
> I confess to not really understanding how the various versions of .Net
> Framework that have been installed on my machines are actually used by
> the application.
>
> So my question is: if the leaks really are fixed in 3.5 SP1, will
> installing that service pack also fix the same leaks in 3.0?
>
> (Of course, only the Beta of 3.5 SP1 is currently available, but I
> could be brave and try it).

From: P Chase on 17 Jun 2008 08:18
On 17 Jun, 13:00, "Alvin Bruney [ASP.NET MVP]" <vapor dan using hot
male spam filter> wrote:
> what memory leak are you seeing? You need to describe it better and give
> some more details.
>
> --
>
> Regards,
> Alvin Bruney [MVP ASP.NET]
>
> [Shameless Author plug]
> The O.W.C. Black Book, 2nd Edition
> Exclusively onwww.lulu.com/owc$19.99
> -------------------------------------------------------
>
> "P Chase" <peter.ch...(a)globalgraphics.com> wrote in message
>
> news:9f5a9847-26a7-4c2d-802e-a4b826b619f7(a)t54g2000hsg.googlegroups.com...
>
> > I am developing an application using Visual Studio 2005, Windows XP
> > (or 2003) and C#. I am using facilities of .Net Framework 3.0, but not
> > of 3.5.
>
> > I am falling foul of some memory leaks in the framework, which
> > Microsoft claim to have fixed in .Net Framework 3.5 SP1.
>
> > I confess to not really understanding how the various versions of .Net
> > Framework that have been installed on my machines are actually used by
> > the application.
>
> > So my question is: if the leaks really are fixed in 3.5 SP1, will
> > installing that service pack also fix the same leaks in 3.0?
>
> > (Of course, only the Beta of 3.5 SP1 is currently available, but I
> > could be brave and try it).

My question was not intended to be about the specific issue I am
facing, but the general issue of whether patching .Net Framework 3.5
would also affect my code which is a client of .Net Framework 3.0. I
don't understand how the various versions of .Net that have been
installed interact.

However, since you ask, I can also give details of the specific issue
I am trying to resolve.

I have a server application that uses FlowDocument to turn some text
and images into a nice-looking document. The FlowDocument is
constructed from XAML.

If the FlowDocument has no images in it, then when I am finished with
it, all memory is happily released. But if there are Image elements in
the XAML, then lots of memory is leaked, and the files providing the
image contents are held open.

I read that some image-related leaks in .Net Framework itself are
fixed by 3.5 SP1. So I want to know whether these might fix my issues.
I hoped to get an indication of the likelihood of this, before going
to the trouble of installing SP1, particularly if it might be
difficult to uninstall.

http://blogs.msdn.com/jgoldb/archive/2008/05/04/memory-leaks-in-wpf-based-applications-blog-update.aspx
From: Rory Becker on 17 Jun 2008 08:52
Hello P,

> I am developing an application using Visual Studio 2005, Windows XP
> (or 2003) and C#. I am using facilities of .Net Framework 3.0, but not
> of 3.5.
>
> I am falling foul of some memory leaks in the framework, which
> Microsoft claim to have fixed in .Net Framework 3.5 SP1.

I would also check to see if your issues are not already cleared up by .Net
3.0 SP1

This would have been installed (I think) by an installation of .Net 3.5 (
If you have that present on your machine) however it is available from http://www.microsoft.com/downloads/details.aspx?familyid=EC2CA85D-B255-4425-9E65-1E88A0BDB72A&displaylang=en


> I confess to not really understanding how the various versions of .Net
> Framework that have been installed on my machines are actually used by
> the application.

Typically an application attempts to "use" the version of the framework that
it was compiled against. If this is not available I believe it will use the
latest available verion. this only applies to 1.0, 1.1 and 2.0 however. 3.0
and 3.5 use the 2.0 verion of the CLR and so may be considered to be additions
to the 2.0 libraries. This is much the same as if you had included third
party libraries in your app

> So my question is: if the leaks really are fixed in 3.5 SP1, will
> installing that service pack also fix the same leaks in 3.0?

Hard to say. I would have expected such things fixed in say 3.0 SP2 which
may itself be included in 3.5 SP1.

But this is Microsoft, and with the best will in the world, general consensus
(although not unanimous) is that they have issues with their versioning within
..Net. Nothing wrong as such, just a touch difficult to follow sometimes :)

> (Of course, only the Beta of 3.5 SP1 is currently available, but I
> could be brave and try it).

Do yourself a favour and don't "Try" anything on a machine you are not prepared
to have die on you. I'm not trying to suggest that this will happen, but
I've found it really pays to be careful with anything beta

I'm really not sure how helpful any of this will be to you but hopefully
something will be :)

--
Rory



From: P Chase on 17 Jun 2008 09:17
On 17 Jun, 13:52, Rory Becker <rorybec...(a)newsgroup.nospam> wrote:
> Hello P,
>
> > I am developing an application using Visual Studio 2005, Windows XP
> > (or 2003) and C#. I am using facilities of .Net Framework 3.0, but not
> > of 3.5.
>
> > I am falling foul of some memory leaks in the framework, which
> > Microsoft claim to have fixed in .Net Framework 3.5 SP1.
>
> I would also check to see if your issues are not already cleared up by .Net
> 3.0 SP1
>
> This would have been installed (I think) by an installation of .Net 3.5 (
> If you have that present on your machine) however it is available fromhttp://www.microsoft.com/downloads/details.aspx?familyid=EC2CA85D-B25...
>
> > I confess to not really understanding how the various versions of .Net
> > Framework that have been installed on my machines are actually used by
> > the application.
>
> Typically an application attempts to "use" the version of the framework that
> it was compiled against. If this is not available I believe it will use the
> latest available verion. this only applies to 1.0, 1.1 and 2.0 however. 3.0
> and 3.5 use the 2.0 verion of the CLR and so may be considered to be additions
> to the 2.0 libraries. This is much the same as if you had included third
> party libraries in your app
>
> > So my question is: if the leaks really are fixed in 3.5 SP1, will
> > installing that service pack also fix the same leaks in 3.0?
>
> Hard to say. I would have expected such things fixed in say 3.0 SP2 which
> may itself be included in 3.5 SP1.
>
> But this is Microsoft, and with the best will in the world, general consensus
> (although not unanimous) is that they have issues with their versioning within
> .Net. Nothing wrong as such, just a touch difficult to follow sometimes :)
>
> > (Of course, only the Beta of 3.5 SP1 is currently available, but I
> > could be brave and try it).
>
> Do yourself a favour and don't "Try" anything on a machine you are not prepared
> to have die on you. I'm not trying to suggest that this will happen, but
> I've found it really pays to be careful with anything beta
>
> I'm really not sure how helpful any of this will be to you but hopefully
> something will be :)
>
> --
> Rory

Thanks for your help.

I already have the latest non-beta Service Packs of everything. So I
think that the beta of 3.5 SP1 is my only hope for an instant fix. But
not sure if I dare try it, particularly as I don't really know whether
the leaks fixed in 3.5 SP1 are the ones I'm experiencing.
 |  Next  |  Last
Pages: 1 2
Prev: Assembly missing in GAC after Publish?
Next: trying out UDP socket, and failing.... (on Vista)