"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