| View previous topic :: View next topic |
| Author |
Message |
Atmapuri Guest
|
Posted: Mon Dec 27, 2004 8:02 am Post subject: Update #1 and memory leaks! |
|
|
Hi!
For those that still expirience memory leaks with
Update #1:
The severity of the memory leaks is proportional
to size of the source file being edited.
To completely resolve them:
Remove or rename the following packages
to disable Together:
"tgide90.bpl"
"borland.studio.together.dll"
in the Bin directory.
It is not sufficient to disable Together from the Project
menu!!! The memory leaks due to Together will
happen as soon as you use the code editor and while
the Delphi is starting.
After you have disabled Together, you will notice, that
memory usage after D2005 has started is only half
of what it is otherwise. (85MB instead of 200 or so). The size
of the memory allocated by the process can be checked accurately with
this tool:
http://www.sysinternals.com/ntw2k/freeware/procexp.shtml
The Windows page file usage is not very accurate. But you get
a .NET and W32 side breakdown with that tool.
To get a .NET garbage collector breakdown use this:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenethowto13.asp
You will be able to see the culprit (Together) on the work.
With the original release of D2005 there were memory leaks in
the code editor itself also. Even without Together.
Those have been fixed with Update #1.
I also found the IDE much more stable and reporting more
usefull error message after disabling Together.
I hope some will find this usefull.
Best Regards!
Atmapuri.
|
|
| Back to top |
|
 |
Derek Davidson Guest
|
Posted: Mon Dec 27, 2004 10:18 am Post subject: Re: Update #1 and memory leaks! |
|
|
Atmapuri wrote:
| Quote: | I hope some will find this usefull.
|
Great info. Thanks :-)
--
Derek Davidson
http://www.ebsms.com
Send SMS Text messages from your PC. For FREE!
|
|
| Back to top |
|
 |
Lars O. Soderstrom Guest
|
Posted: Mon Dec 27, 2004 4:07 pm Post subject: Re: Update #1 and memory leaks! |
|
|
Seems like it helps a lot, thanks!
Lars
"Atmapuri" <janez.makovsek (AT) usa (DOT) net> skrev i meddelandet
news:41cfc18a (AT) newsgroups (DOT) borland.com...
| Quote: | Hi!
For those that still expirience memory leaks with
Update #1:
The severity of the memory leaks is proportional
to size of the source file being edited.
To completely resolve them:
Remove or rename the following packages
to disable Together:
"tgide90.bpl"
"borland.studio.together.dll"
in the Bin directory.
It is not sufficient to disable Together from the Project
menu!!! The memory leaks due to Together will
happen as soon as you use the code editor and while
the Delphi is starting.
After you have disabled Together, you will notice, that
memory usage after D2005 has started is only half
of what it is otherwise. (85MB instead of 200 or so). The size
of the memory allocated by the process can be checked accurately with
this tool:
http://www.sysinternals.com/ntw2k/freeware/procexp.shtml
The Windows page file usage is not very accurate. But you get
a .NET and W32 side breakdown with that tool.
To get a .NET garbage collector breakdown use this:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenethowto13.asp
You will be able to see the culprit (Together) on the work.
With the original release of D2005 there were memory leaks in
the code editor itself also. Even without Together.
Those have been fixed with Update #1.
I also found the IDE much more stable and reporting more
usefull error message after disabling Together.
I hope some will find this usefull.
Best Regards!
Atmapuri.
|
|
|
| Back to top |
|
 |
Dennis Landi Guest
|
Posted: Mon Dec 27, 2004 5:53 pm Post subject: Re: Update #1 and memory leaks! |
|
|
Remind me again, what the Together stuff is for?
Do I need it for ECO II?
-d
|
|
| Back to top |
|
 |
dk_sz Guest
|
Posted: Mon Dec 27, 2004 6:52 pm Post subject: Re: Update #1 and memory leaks! |
|
|
| Quote: | "tgide90.bpl"
"borland.studio.together.dll"
in the Bin directory.
|
Will Delphi autoload it again if one renames/places "tgide90.bpl"
back? (e.g. when Borland fixes the memory leaks)
best regards
Thomas Schulz
|
|
| Back to top |
|
 |
Kevin Berry Guest
|
Posted: Mon Dec 27, 2004 7:23 pm Post subject: Re: Update #1 and memory leaks! |
|
|
Atmapuri wrote:
| Quote: | I hope some will find this usefull.
Best Regards!
Atmapuri.
|
OK, but what do you lose by disabling it? I use Delphi 2005
Professional. Does this affect me?
Thanks,
Kevin.
|
|
| Back to top |
|
 |
Lars O. Soderstrom Guest
|
Posted: Tue Dec 28, 2004 12:39 am Post subject: Re: Update #1 and memory leaks! |
|
|
Well, you get a question on startup if you would like to try to load the
packages at next startup. If you choose 'Yes' and restore the files, Delphi
will try to load the packages at next start.
Lars
"dk_sz" <dk_sz (AT) hotmail (DOT) com> skrev i meddelandet
news:41d06698 (AT) newsgroups (DOT) borland.com...
| Quote: | "tgide90.bpl"
"borland.studio.together.dll"
in the Bin directory.
Will Delphi autoload it again if one renames/places "tgide90.bpl"
back? (e.g. when Borland fixes the memory leaks)
best regards
Thomas Schulz
|
|
|
| Back to top |
|
 |
Philip Hofstetter Guest
|
Posted: Tue Dec 28, 2004 12:47 am Post subject: Re: Update #1 and memory leaks! |
|
|
Hi,
Atmapuri wrote:
| Quote: | To completely resolve them:
Remove or rename the following packages
to disable Together:
|
This seems to have fixed my problems with ErrorInsight as well.
Before disabling those packages, sometimes, ErrorInsight complained
about unknown types which definititely were not unknown at all (like
TObject for example). Needless to say that the units compiled without
errors too.
And Delphi seems to feel a bit faster too, though this may just be my
imagination...
Thanks anyway.
Philip
|
|
| Back to top |
|
 |
Atmapuri Guest
|
Posted: Tue Dec 28, 2004 7:44 am Post subject: Re: Update #1 and memory leaks! |
|
|
Hi!
| Quote: | OK, but what do you lose by disabling it? I use Delphi 2005
Professional. Does this affect me?
|
It affects ECO II modeling in Delphi.NET and C#. ECO II will still
work, but modeling will not. If you use W32 only
I think you dont loose anything.
But if Together is loaded the W32 side is for my purpose
not really usable. Without it its like breath of life for IDE.
A few things I noticed:
- big projects are loaded instantly.
- memory is no longer a problem, stays very low constantly
- I get compiler errors where there used to be AV's
or just nothing.
-...
Best Regards!
Atmapuri
|
|
| Back to top |
|
 |
Bryce K. Nielsen Guest
|
Posted: Tue Dec 28, 2004 4:13 pm Post subject: Re: Update #1 and memory leaks! |
|
|
| Quote: | It is not sufficient to disable Together from the Project
menu!!! The memory leaks due to Together will
happen as soon as you use the code editor and while
the Delphi is starting.
|
What's the "proper" way to disable Together then? Is it Tools | Together? Do
you have to do each Project? And finally also rename the DLLs?
-BKN
|
|
| Back to top |
|
 |
Holger Flick Guest
|
Posted: Tue Dec 28, 2004 5:41 pm Post subject: Re: Update #1 and memory leaks! |
|
|
Atmapuri,
it's great what you proposed. Everything is way faster now!! I never
used the Together support for my existing projects anyway.
--
Holger
| Quote: | It affects ECO II modeling in Delphi.NET and C#. ECO II will still
work, but modeling will not. If you use W32 only
I think you dont loose anything.
|
|
|
| Back to top |
|
 |
Kyle A. Miller Guest
|
Posted: Tue Dec 28, 2004 6:13 pm Post subject: Re: Update #1 and memory leaks! |
|
|
Atmapuri wrote:
| Quote: | With the original release of D2005 there were memory leaks in
the code editor itself also. Even without Together.
Those have been fixed with Update #1.
I also found the IDE much more stable and reporting more
usefull error message after disabling Together.
|
Can someone from Borland or TeamB verify this? Hopefully a separate
Together patch could be released to fix this.
|
|
| Back to top |
|
 |
Nick Hodges [TeamB] Guest
|
Posted: Tue Dec 28, 2004 6:42 pm Post subject: Re: Update #1 and memory leaks! |
|
|
Kyle A. Miller wrote:
| Quote: | Can someone from Borland or TeamB verify this?
|
I did it and found memory use to be better.
--
Nick Hodges -- TeamB
Lemanix Corporation -- http://www.lemanix.com
Read my Blog -- http://www.lemanix.com/nick
|
|
| Back to top |
|
 |
Captain Jake Guest
|
Posted: Tue Dec 28, 2004 9:36 pm Post subject: Re: Update #1 and memory leaks! |
|
|
Atmapuri <janez.makovsek (AT) usa (DOT) net> wrote in message
<41cfc18a (AT) newsgroups (DOT) borland.com>
| Quote: | The memory leaks due to Together will
happen as soon as you use the code editor and while
the Delphi is starting.
After you have disabled Together, you will notice, that
memory usage after D2005 has started is only half
of what it is otherwise.
|
This is probably one of the best arguments against using Java or .NET or any
other garbage-collected framework, namely that people will interpret the
activities of the garbage-collector as a "memory leak".
--
***Free Your Mind***
Posted with JSNewsreader-BETA 0.9.4.362
|
|
| Back to top |
|
 |
Bryce K. Nielsen Guest
|
Posted: Tue Dec 28, 2004 10:28 pm Post subject: Re: Update #1 and memory leaks! |
|
|
| Quote: | And Delphi seems to feel a bit faster too, though this may just be my
imagination...
|
I've found this to keep the memory leaks WAY down, but the Delphi IDE is
still incredibly slow. When I double-click on a TFrame in my ProjectManager,
about 5 to 8 seconds later does it finally load up in the editor. Going from
Form-to-Code takes upwards of 4 seconds too, and even more annoying, if I
have the Form open and then I click on the editor, the mouseup doesn't get
called until AFTER those 4 seconds are up, so if I move the mouse anywhere
after I click, a whole bunch of text is highlighted (which really sucks,
since I normally just click on the editor and start typing, but now I have
to wait and make sure that nothings highlighted or I lose a bunch of text).
Does your IDE respond faster?
-BKN
|
|
| Back to top |
|
 |
|