Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #9241 > unrolled thread

Closing a VO window crashes to Windows

Started byMartin <Martin@spam.spam>
First post2016-04-11 09:42 +0100
Last post2016-04-28 11:11 +0100
Articles 10 — 4 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Closing a VO window crashes to Windows Martin <Martin@spam.spam> - 2016-04-11 09:42 +0100
    Re: Closing a VO window crashes to Windows Martin <Martin@spam.spam> - 2016-04-11 15:29 +0100
      Re: Closing a VO window crashes to Windows Carlos Rocha <j.carlos.rocha.1.SpyedBy@gmail.com> - 2016-04-11 17:00 +0100
        Re: Closing a VO window crashes to Windows Martin <Martin@spam.spam> - 2016-04-12 12:09 +0100
          Re: Closing a VO window crashes to Windows Martin <Martin@spam.spam> - 2016-04-12 16:13 +0100
            Re: Closing a VO window crashes to Windows James Martin <james@northwoodlumber.com> - 2016-04-12 11:53 -0400
              Re: Closing a VO window crashes to Windows Martin <Martin@spam.spam> - 2016-04-13 09:35 +0100
            Re: Closing a VO window crashes to Windows Otto Christiaanse <ofchristiaanse@gmail.com> - 2016-04-12 23:58 -0700
              Re: Closing a VO window crashes to Windows Martin <Martin@spam.spam> - 2016-04-13 09:29 +0100
    Re: Closing a VO window crashes to Windows Martin <Martin@spam.spam> - 2016-04-28 11:11 +0100

#9241 — Closing a VO window crashes to Windows

FromMartin <Martin@spam.spam>
Date2016-04-11 09:42 +0100
SubjectClosing a VO window crashes to Windows
Message-ID<nefnqg$c3p$1@dont-email.me>
Hello all

We are getting a strange issue with our current build of crashing out to 
Windows with no error.

A few debugs put the crash to somewhere between the last return in the 
window which causes the crash Close method, andthe first line after the 
call to the window.

It is not running out of resources.

VO 2.8 SP4 on a couple of Windows 7 PCs

Does anyone have any ideas where to look as it is driving me mad.

Thanks

Martin

[toc] | [next] | [standalone]


#9243

FromMartin <Martin@spam.spam>
Date2016-04-11 15:29 +0100
Message-ID<negc5u$n3p$1@dont-email.me>
In reply to#9241
Added more debugs, not crashing in Destroy at all as it is reaching the end.

What runs after destroy?

On 11/04/2016 09:42, Martin wrote:
> Hello all
>
> We are getting a strange issue with our current build of crashing out to
> Windows with no error.
>
> A few debugs put the crash to somewhere between the last return in the
> window which causes the crash Close method, andthe first line after the
> call to the window.
>
> It is not running out of resources.
>
> VO 2.8 SP4 on a couple of Windows 7 PCs
>
> Does anyone have any ideas where to look as it is driving me mad.
>
> Thanks
>
> Martin

[toc] | [prev] | [next] | [standalone]


#9244

FromCarlos Rocha <j.carlos.rocha.1.SpyedBy@gmail.com>
Date2016-04-11 17:00 +0100
Message-ID<neghfq$dvl$1@dont-email.me>
In reply to#9243
Hi Martin,

It's probably a try to access some object that doesn't exist anymore. 
Try to check the order objects are destroyed, paying special attention 
to 3rd party ActiveX.

> Added more debugs, not crashing in Destroy at all as it is reaching the
> end.
>
> What runs after destroy?
>
> On 11/04/2016 09:42, Martin wrote:
>> Hello all
>>
>> We are getting a strange issue with our current build of crashing out to
>> Windows with no error.
>>
>> A few debugs put the crash to somewhere between the last return in the
>> window which causes the crash Close method, andthe first line after the
>> call to the window.
>>
>> It is not running out of resources.
>>
>> VO 2.8 SP4 on a couple of Windows 7 PCs
>>
>> Does anyone have any ideas where to look as it is driving me mad.
>>
>> Thanks
>>
>> Martin
>


-- 
*Carlos Rocha*

---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus

[toc] | [prev] | [next] | [standalone]


#9251

FromMartin <Martin@spam.spam>
Date2016-04-12 12:09 +0100
Message-ID<neikre$c6h$1@dont-email.me>
In reply to#9244
I will check that, do you know where that code is?

I thought I had found it yesterday but I had not.

The crash is somewhere between the PostQuitMessage (after close and 
destroy) deep in a supered Dispatch and the first line of code it does 
not reach is a log in the parent call just after show

Thanks

Martin

On 11/04/2016 17:00, Carlos Rocha wrote:
> Hi Martin,
>
> It's probably a try to access some object that doesn't exist anymore.
> Try to check the order objects are destroyed, paying special attention
> to 3rd party ActiveX.
>
>> Added more debugs, not crashing in Destroy at all as it is reaching the
>> end.
>>
>> What runs after destroy?
>>
>> On 11/04/2016 09:42, Martin wrote:
>>> Hello all
>>>
>>> We are getting a strange issue with our current build of crashing out to
>>> Windows with no error.
>>>
>>> A few debugs put the crash to somewhere between the last return in the
>>> window which causes the crash Close method, andthe first line after the
>>> call to the window.
>>>
>>> It is not running out of resources.
>>>
>>> VO 2.8 SP4 on a couple of Windows 7 PCs
>>>
>>> Does anyone have any ideas where to look as it is driving me mad.
>>>
>>> Thanks
>>>
>>> Martin
>>
>
>

[toc] | [prev] | [next] | [standalone]


#9252

FromMartin <Martin@spam.spam>
Date2016-04-12 16:13 +0100
Message-ID<nej34j$3a0$1@dont-email.me>
In reply to#9251
OK more tests and I am getting really desperate now!!!!

Objects on the screen are being destroyed and the crash is between the 
deep down dispatch code

	CASE (oEvent:message == WM_CLOSE)
		IF SELF:QueryClose(oEvent)
			SELF:__Close(oEvent)
			IF lQuitOnClose
				PostQuitMessage(0)
			ENDIF
		ENDIF

//A debug is OK here and works
		RETURN SELF:EventReturnValue

And a modified show where all super code is included in my class

     IF SELF:lValidFlag
//	From dataWindow:Show() & ChildAppWindow:Show()
         IF !lSubForm
             // Show oFormFrame as SHOWNORMAL in case data window is 
//shown iconized
             IF self:dwDialogStyle = 0   //SE-120204
			    IF (oImp != NULL_OBJECT)
			        RETURN oImp:Show(nShowState)
			    ENDIF
                 oFormFrame:Show(SHOWNORMAL)
             ELSE // DataDialog
                 oFormFrame:Show(SHOWNORMAL)
                 SetFocus(oSurface:Handle())
			    IF (oImp != NULL_OBJECT)
// this place debug is OK
					uVal	:= oImp:Show(nShowState)
// this place is not always reached
			        RETURN uVal
			    ENDIF
                 RETURN SELF
             ENDIF
         ELSE
             oFormFrame:Show(nShowState)
         ENDIF


oImp is of class __DDIMP if that is of any use

I have looked through the show code and cannot find where the dispatch 
handler gets started and used, so do not know what line of code stops 
until I hit escape

[toc] | [prev] | [next] | [standalone]


#9253

FromJames Martin <james@northwoodlumber.com>
Date2016-04-12 11:53 -0400
Message-ID<nej5da$bco$1@dont-email.me>
In reply to#9252
I had this happen to me years ago and if I remember right it had to do 
with something outside of VO - OLE, ODBC, Advantage database - or 
something like that. Is there anything outside of VO code in the window?

James

On 16-04-12 11:13 AM, Martin wrote:
> OK more tests and I am getting really desperate now!!!!
>
> Objects on the screen are being destroyed and the crash is between the
> deep down dispatch code
>
>      CASE (oEvent:message == WM_CLOSE)
>          IF SELF:QueryClose(oEvent)
>              SELF:__Close(oEvent)
>              IF lQuitOnClose
>                  PostQuitMessage(0)
>              ENDIF
>          ENDIF
>
> //A debug is OK here and works
>          RETURN SELF:EventReturnValue
>
> And a modified show where all super code is included in my class
>
>      IF SELF:lValidFlag
> //    From dataWindow:Show() & ChildAppWindow:Show()
>          IF !lSubForm
>              // Show oFormFrame as SHOWNORMAL in case data window is
> //shown iconized
>              IF self:dwDialogStyle = 0   //SE-120204
>                  IF (oImp != NULL_OBJECT)
>                      RETURN oImp:Show(nShowState)
>                  ENDIF
>                  oFormFrame:Show(SHOWNORMAL)
>              ELSE // DataDialog
>                  oFormFrame:Show(SHOWNORMAL)
>                  SetFocus(oSurface:Handle())
>                  IF (oImp != NULL_OBJECT)
> // this place debug is OK
>                      uVal    := oImp:Show(nShowState)
> // this place is not always reached
>                      RETURN uVal
>                  ENDIF
>                  RETURN SELF
>              ENDIF
>          ELSE
>              oFormFrame:Show(nShowState)
>          ENDIF
>
>
> oImp is of class __DDIMP if that is of any use
>
> I have looked through the show code and cannot find where the dispatch
> handler gets started and used, so do not know what line of code stops
> until I hit escape

[toc] | [prev] | [next] | [standalone]


#9260

FromMartin <Martin@spam.spam>
Date2016-04-13 09:35 +0100
Message-ID<nel05f$gov$1@dont-email.me>
In reply to#9253
It is using ADS of course, all data access is via it.

There is also some C code called for shape designing.

Howver an older build does not seem to crash as much. And it uses all 
the same DLLs.

This is driving me mad!

Thanks

Martin

On 12/04/2016 16:53, James Martin wrote:
> I had this happen to me years ago and if I remember right it had to do
> with something outside of VO - OLE, ODBC, Advantage database - or
> something like that. Is there anything outside of VO code in the window?
>
> James
>
> On 16-04-12 11:13 AM, Martin wrote:
>> OK more tests and I am getting really desperate now!!!!
>>
>> Objects on the screen are being destroyed and the crash is between the
>> deep down dispatch code
>>
>>      CASE (oEvent:message == WM_CLOSE)
>>          IF SELF:QueryClose(oEvent)
>>              SELF:__Close(oEvent)
>>              IF lQuitOnClose
>>                  PostQuitMessage(0)
>>              ENDIF
>>          ENDIF
>>
>> //A debug is OK here and works
>>          RETURN SELF:EventReturnValue
>>
>> And a modified show where all super code is included in my class
>>
>>      IF SELF:lValidFlag
>> //    From dataWindow:Show() & ChildAppWindow:Show()
>>          IF !lSubForm
>>              // Show oFormFrame as SHOWNORMAL in case data window is
>> //shown iconized
>>              IF self:dwDialogStyle = 0   //SE-120204
>>                  IF (oImp != NULL_OBJECT)
>>                      RETURN oImp:Show(nShowState)
>>                  ENDIF
>>                  oFormFrame:Show(SHOWNORMAL)
>>              ELSE // DataDialog
>>                  oFormFrame:Show(SHOWNORMAL)
>>                  SetFocus(oSurface:Handle())
>>                  IF (oImp != NULL_OBJECT)
>> // this place debug is OK
>>                      uVal    := oImp:Show(nShowState)
>> // this place is not always reached
>>                      RETURN uVal
>>                  ENDIF
>>                  RETURN SELF
>>              ENDIF
>>          ELSE
>>              oFormFrame:Show(nShowState)
>>          ENDIF
>>
>>
>> oImp is of class __DDIMP if that is of any use
>>
>> I have looked through the show code and cannot find where the dispatch
>> handler gets started and used, so do not know what line of code stops
>> until I hit escape

[toc] | [prev] | [next] | [standalone]


#9258

FromOtto Christiaanse <ofchristiaanse@gmail.com>
Date2016-04-12 23:58 -0700
Message-ID<d201831a-19ec-4843-90d5-d3fabc64ed52@googlegroups.com>
In reply to#9252
On Tuesday, April 12, 2016 at 5:13:32 PM UTC+2, Martin wrote:
> OK more tests and I am getting really desperate now!!!!
> 

I know this isn't the answer that you / we are looking for, but, can't you just try to catch the crash the error, log it and continue?

I'm afraid to see what responses I will get for this suggestion...

[toc] | [prev] | [next] | [standalone]


#9259

FromMartin <Martin@spam.spam>
Date2016-04-13 09:29 +0100
Message-ID<nekvr8$f7g$1@dont-email.me>
In reply to#9258
It is not crashing via the error system, it just bombs out to windows, 
instant program shut down

On 13/04/2016 07:58, Otto Christiaanse wrote:
> On Tuesday, April 12, 2016 at 5:13:32 PM UTC+2, Martin wrote:
>> OK more tests and I am getting really desperate now!!!!
>>
>
> I know this isn't the answer that you / we are looking for, but, can't you just try to catch the crash the error, log it and continue?
>
> I'm afraid to see what responses I will get for this suggestion...
>

[toc] | [prev] | [next] | [standalone]


#9300

FromMartin <Martin@spam.spam>
Date2016-04-28 11:11 +0100
Message-ID<nfsndb$sjp$1@dont-email.me>
In reply to#9241
Have an answer and...........

It was calling some checking code after the screen was shut down, no 
idea how it got called, but fixed it by using an instance of a data 
server opened in the parent rather than on the screen.

very odd

On 11/04/2016 09:42, Martin wrote:
> Hello all
>
> We are getting a strange issue with our current build of crashing out to
> Windows with no error.
>
> A few debugs put the crash to somewhere between the last return in the
> window which causes the crash Close method, andthe first line after the
> call to the window.
>
> It is not running out of resources.
>
> VO 2.8 SP4 on a couple of Windows 7 PCs
>
> Does anyone have any ideas where to look as it is driving me mad.
>
> Thanks
>
> Martin

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web