Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: Memoery Leak Problem


This question is not answered. Helpful answers available: 1. Correct answers available: 1.


Permlink Replies: 5 - Last Post: Sep 18, 2016 2:19 PM Last Post By: Gary Wardell
Gary Wardell

Posts: 241
Registered: 11/13/03
Memoery Leak Problem  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 5, 2016 3:33 PM
Hi,

So how do I work around this? Or do I just ignore it?

I created a test app with this code and not much else:

procedure TForm1.FormCreate(Sender: TObject);
const
  StyleRoot: string = 'E:\Users\gwardell\Documents\BullsEyeChirp\Styles\';
  StyleName: string = 'Main.style';
 
var
  VStyleFile: string;
 
begin
  Self.BeginUpdate;
  Self.StyleBook := nil;
  VStyleFile := StyleRoot + StyleName;
  if FileExists(VStyleFile) then
  begin
    StyleBook1.FileName := VStyleFile;
  end;
 
  Self.StyleBook := StyleBook1;
  Self.EndUpdate;
end;
 
and elsewhere
 
  ReportMemoryLeaksOnShutdown := True;


It runs without error. But when I close the form I get this:

---------------------------
Unexpected Memory Leak
---------------------------
An unexpected memory leak has occurred. The unexpected small block leaks are:
 
21 - 28 bytes: TMemoryStream x 43
 
The sizes of unexpected leaked medium and large blocks are: 228396, 256300, 8236, 8236, 8236, 
8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 
8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 8236, 
8236, 8236, 8236, 8236, 8236, 458732
---------------------------
OK   
---------------------------


But if I comment out this line there is no leak.

//    StyleBook1.FileName := VStyleFile;


So, Is there anything I can to to not have this problem, or do I just ignore it since it's not in my code?

Gary
Delphi Seattle, FireMonkey, Win32

Edited by: Gary Wardell on Jul 5, 2016 3:34 PM
Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: Memoery Leak Problem
Helpful
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 7, 2016 5:56 PM   in response to: Gary Wardell in response to: Gary Wardell
Gary Wardell wrote:
So how do I work around this? Or do I just ignore it?

Known problem in Seattle, fixed in Berlin.

Memory Leaks when using TStyleBook.Filename property
https://quality.embarcadero.com/browse/RSP-12807

Memory leaks in TStyleStreaming.SaveToIndexedStream
https://quality.embarcadero.com/browse/RSP-11335

--
Remy Lebeau (TeamB)
Gary Wardell

Posts: 241
Registered: 11/13/03
Re: Memoery Leak Problem  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 7, 2016 7:29 PM   in response to: Remy Lebeau (Te... in response to: Remy Lebeau (Te...
Remy Lebeau (TeamB) wrote:
Gary Wardell wrote:
So how do I work around this? Or do I just ignore it?

Known problem in Seattle, fixed in Berlin.

Memory Leaks when using TStyleBook.Filename property
https://quality.embarcadero.com/browse/RSP-12807

Memory leaks in TStyleStreaming.SaveToIndexedStream
https://quality.embarcadero.com/browse/RSP-11335

--
Remy Lebeau (TeamB)

Ok, well, my support lapsed due to lack of funds.

I guess there is no patch for Seattle.

Are other Seattle memory problems fixed. I know of at least one other in Firedac.

Gary
Linden ROTH

Posts: 467
Registered: 11/3/11
Re: Memoery Leak Problem  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 7, 2016 9:19 PM   in response to: Gary Wardell in response to: Gary Wardell
Gary Wardell wrote:
Remy Lebeau (TeamB) wrote:
Gary Wardell wrote:
So how do I work around this? Or do I just ignore it?

Known problem in Seattle, fixed in Berlin.

--
Remy Lebeau (TeamB)

Ok, well, my support lapsed due to lack of funds.

I guess there is no patch for Seattle.

Are other Seattle memory problems fixed. I know of at least one other in Firedac.

Gary

This might help ...

Brandon Shopp - IDERA leads product management team - wrote:

•RAD Studio Berlin 10.1 Backports for XE8 and 10 Seattle – this is in active development right now


http://community.embarcadero.com/blogs?view=entry&id=8596?utm_source=cgeb&utm_medium=email&utm_campaign=newsletter&utm_term=ww-en&utm_content=160707-weekly-nl

--
Linden
"Mango" was Cool but "Wasabi" was Hotter but remember it's all in the "source"

Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: Memoery Leak Problem  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 8, 2016 11:35 AM   in response to: Gary Wardell in response to: Gary Wardell
Gary wrote:

I guess there is no patch for Seattle.

Not yet, but fixes in Berlin are in progress of being backported to XE8 and
Seattle.

--
Remy Lebeau (TeamB)
Gary Wardell

Posts: 241
Registered: 11/13/03
Re: Memoery Leak Problem  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 18, 2016 2:19 PM   in response to: Remy Lebeau (Te... in response to: Remy Lebeau (Te...
Is there a fix for Seattle yet?
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02