Prev: Set Window Owner
Next: VO 2.8:I am VERY ANGRY ......
From: tlfpgs on 6 Oct 2008 13:40
On 5 oct, 03:00, "Stephen Quinn" <stevej...(a)SPbigpond.AMnet.au> wrote:
> Thierry
>
> DynSize() maybe, what setting are you currently using??
>
> CYA
> Steve

Hi Steve,

I didn't use DynSize() up to now.
I provide a new version of my application with DynSize(30) in
App:Start().
Waiting the feed back to see if it helps.

Thierry
From: tlfpgs on 6 Oct 2008 13:45
On 6 oct, 16:38, Karl Wochele <kw_nosp...(a)ecos-system.de> wrote:
> Thierry,
>
> there is a limit of 10000 GUI-Objects in Windows. Above this limit your
> app will crash. You can check the amount of objects with
>
> nObjects := GetGuiResources(GetCurrentProcess(),GR_GDIOBJECTS))
>
> _DLL FUNC GetGuiResources(hProcess AS PTR,uiFlags AS DWORD) AS DWORD
> PASCAL:USER32.GetGuiResources
> DEFINE GR_GDIOBJECTS    := 0
> DEFINE GR_USEROBJECTS   := 1
>
> If this number is growing, you have a leak somewhere in your code, such
> as icons, bitmaps or device contexts which are not released.
>
> HTH
> Karl
>
> tlf...(a)gmail.com schrieb:
>
> > Hi to all,
>
> > According many of my customers, the following errors occur randomly in
> > my
> > application :
>
> > "Dialog creation from resource failed"
> > in the DIALOGWINDOW:INIT method
>
> > or
>
> > "Control creation failed"
> > Function : CONTROL:CREATE
> > Argument : #PRICHEDITOLE:, Type : OBJECT
> > Description : PRICHEDIT:HANDLE (Line: 5)
> > when creating controls either dynamically or from a resource
>
> > or
>
> > Function : RESOURCEID:INIT
> > Description : Invalid argument type.
> > PFDATAWINDOW:INIT (Line: 10)
>
> > These errors occur after several hours of use of the application.
> > Never at
> > starting or using it few minutes, so it's very difficult to reproduce.
> > It seems to be related to the memory management, but how prevent or
> > correct
> > them ?
>
> > Thanks for any help on that point,
>
> > Thierry Le Floch
>
>

Hi Karl,

Thanks for the tip. I will include that in my application.
In fact, I'm suspecting the Riched32.dll we are still using to handle
RTF with embedded objects. 5 years ago, we got similar problems which
were fixed by providing with our application the Riched32.dll from
Windows 98 in replacement of the one available in Xp. It seems that
the Riched32.dll from Xp doesn't release resources correctly when a
windows with a Rtf control is closed.

Thierry


From: Arne Ortlinghaus on 8 Oct 2008 09:50
Yes, I can confirm also that dialogs with the RTF control do not release all
objects. I did not realize that before. It is at least one of our "memory
leaks".

Arne Ortlinghaus
ACS Data Systems


 | 
Pages: 1
Prev: Set Window Owner
Next: VO 2.8:I am VERY ANGRY ......