Error in deployed application's message loop

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Error in deployed application's message loop

David Gorisek-5
Hello,

does anyone know what could cause this error (see below)? It happens
very very often, but the application continues to run without problems.

Thanks and best regards,

David Gorisek


----
Description: Invalid access to memory location. Writing 0x7CE549C, IP
0x7CE549C ()[Unrecognised HRESULT - 16rD0000005]
a GPFault('Invalid access to memory location. Writing 0x7CE549C, IP
0x7CE549C ()')

ProcessorScheduler>>gpFault:
[] in ProcessorScheduler>>vmi:list:no:with:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>vmi:list:no:with:
UserLibrary(ExternalLibrary)>>invalidCall
UserLibrary>>enumWindows:lParam:
InputState>>topLevelHandlesDo:
InputState>>uiIdle
InputState>>aboutToIdle
InputState>>messageLoopIdle
InputState>>loopWhile:
InputState>>mainLoop
[] in InputState>>forkMain
ExceptionHandler(ExceptionHandlerAbstract)>>markAndTry
[] in ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>ifCurtailed:
BlockClosure>>ensure:
ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>on:do:
[] in BlockClosure>>newProcess


Reply | Threaded
Open this post in threaded view
|

Re: Error in deployed application's message loop

Chris Uppal-3
David,

> does anyone know what could cause this error (see below)? It happens
> very very often, but the application continues to run without problems.

That's a new one.  If you look in the archives (or Google) for
topLevelHandlesDo then you'll find a few odd stories involving:

> InputState>>topLevelHandlesDo:

but this is the first report where the application continued to work
afterwards.

Several of them seem to be related to Window's Data Execution Protection (which
doesn't like the way that Dolphin creates executable thunks in memory as the
"glue" to implement external callbacks).  I /think/ Blair said that'll be fixed
in the next patch.  If not, or until then, you can turn DEP off on a
per-application basis.

Otherwise, two questions: is this a GUI application, and what OS/hardware is it
running on ?

    -- chris


Reply | Threaded
Open this post in threaded view
|

Re: Error in deployed application's message loop

Blair McGlashan-4
"Chris Uppal" <[hidden email]> wrote in message
news:446dabec$0$648$[hidden email]...

> David,
>
>> does anyone know what could cause this error (see below)? It happens
>> very very often, but the application continues to run without problems.
>
> That's a new one.  If you look in the archives (or Google) for
> topLevelHandlesDo then you'll find a few odd stories involving:
>
>> InputState>>topLevelHandlesDo:
>
> but this is the first report where the application continued to work
> afterwards.
>
> Several of them seem to be related to Window's Data Execution Protection
> (which
> doesn't like the way that Dolphin creates executable thunks in memory as
> the
> "glue" to implement external callbacks).  I /think/ Blair said that'll be
> fixed
> in the next patch.  If not, or until then, you can turn DEP off on a
> per-application basis.
>

Execution on DEP-enabled machine/OS combinations was already supported in
Dolphin 6 (but then I'd guess this is not 6.02 because it does not define
InputState>>topLevelHandlesDo:), and is now supported in the recently
released Dolphin 5.1.5.

Regards

Blair