Ron:
We use very few memvars, and none that I can see in the involved code.

We're looking at prg code that's been basically working since 
the dawn of xHarbour.  But in the early days of Fivewin we
sometimes had to hack to make things work, and some of the
old code is certainly not what we'd write today from scratch.

The size of the data and arrays is not the issue, BTW.

We're looking at whether passing a STATIC array BY REFERENCE 
to funcs in other prgs (and in some cases the same prg)
that may reassign it could be part of the picture; that's some
of the more odd code involved.
So a locally received arg that hides a file wide static that
happens to be the same item gets reassigned, so prior contents
would have to be cleared.  Does something clear it twice?

Sounds suspicious, but small tests haven't isolated it yet.

--
Brian Hays


> -----Original Message-----
> From: Ron Pinkas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 05, 2008 5:30 PM
> To: Ron Pinkas
> Cc: bhays; 'xHarbour-Developers'
> Subject: Re: [xHarbour-developers] PREMATURE ARRAY/OBJECT RELEASE
> DETECTED O 16BA914
> 
> Brian,
> 
> Just as important:
> 
> We never since received any additional report of the premature
> release error, and I'm aware of number of complex applications using
> current CVS. If the problem is in xHarbour I'd guess it must be
> related to less frequently used, MEMVARs.
> 
> Ron
> 
> On Jun 5, 2008, at 4:59 PM, Ron Pinkas wrote:
> 
> > FWIW,
> >
> > IIRC, just after that first change was introduced, we did have few
> > reports of the premature release error, which then appear to have
> > been resolved by the followup correction by Walter.
> >
> > Ron
> >
> > On Jun 5, 2008, at 4:46 PM, Ron Pinkas wrote:
> >
> >> Brian,
> >>
> >> This happens when an Array or Object is being released, and LATER
> >> some C code calls hb_itemClear( pItem )  or indirectly by means of
> >> hb_itemRelease( pItem ).
> >>
> >> The last changes that might be related were:
> >>
> >>     2008-01-10 11:47 UTC+0100 Miguel Angel Marchuet <miguelangel/at/
> >> marchuet.net>
> >>     2008-01-14 11:00 UTC-0200 Walter Negro <anegro/at/
> >> overnet.com.ar >
> >>
> >> Otherwise I'm not aware of any core change that might be related, in
> >> very long time.
> >>
> >> I'd add traces to hb_arrayNew() as well as  hb_arrayReleaseBase()
> and
> >> hb_arrayReleaseGarbage() to track the creation and release of each
> >> array, and I'd log pBaseArray as well as pBaseArray->uiClass (when
> in
> >> hb_arrayReleaseBase() and hb_arrayReleaseGarbage()).
> >>
> >> I'll shortly also add an assert(0) just before that error is raised,
> >> so that a Debug Build will trigger your debugger, where you may
> >> discover more details.
> >>
> >> Ron
> >>
> >> On Jun 5, 2008, at 11:32 AM, bhays wrote:
> >>
> >>> This is a CRITICAL error.
> >>>
> >>> Users of my full Fivewin app are getting this Unrecoverable error
> >>> when closing an MDI child window.
> >>> This is when the garbage collector gets invoked (there are dialogs
> >>> on my MDI windows, and FWH calls hb_gcAll() upon closing a dialog).
> >>>
> >>> There are other MDI child windows open, there's no attempt to close
> >>> the app.
> >>>
> >>> It's intermittent but pretty common and can happen within 5
> >>> minutes of
> >>> using the program.  We have NOT been able to reduce the steps to
> >>> create the problem, let alone create a small sample.
> >>>
> >>> This is the first build using the xHarbour CVS since a few months
> >>> back.
> >>> We have never seen this before in my app.
> >>>
> >>> Any ideas how to put enough traces in to narrow down the cause?
> >>>
> >>> --
> >>> Brian Hays
> >>>
> >>>
> >>>
> >>>
> >>> -------------------------------------------------------------------
> -
> >>> -
> >>> -
> >>> ---
> >>> Check out the new SourceForge.net Marketplace.
> >>> It's the best place to buy or sell services for
> >>> just about anything Open Source.
> >>> http://sourceforge.net/services/buy/index.php
> >>> _______________________________________________
> >>> xHarbour-developers mailing list
> >>> [email protected]
> >>> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
> >>>
> >>
> >>
> >>
> >> --------------------------------------------------------------------
> -
> >> -
> >> ---
> >> Check out the new SourceForge.net Marketplace.
> >> It's the best place to buy or sell services for
> >> just about anything Open Source.
> >> http://sourceforge.net/services/buy/index.php
> >> _______________________________________________
> >> xHarbour-developers mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> -
> > ---
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://sourceforge.net/services/buy/index.php
> > _______________________________________________
> > xHarbour-developers mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/xharbour-developers
> >
> 
> 
> No virus found in this incoming message.
> Checked by AVG.
> Version: 8.0.100 / Virus Database: 270.0.0/1485 - Release Date:
> 6/5/2008 10:07 AM


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
xHarbour-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xharbour-developers

Reply via email to