Hi
Another interesting result which is a surprise to me is that the issue
is reproducible when passing a pointer within the host. So, in the
end, it has nothing to do with components.
I've been under the impression the whole time that the problem was
passing a pointer across the host-component interface, however when I
replaced the component method with a host one, the host method also
runtime errors when trying to de-reference the pointer.
Sorry that this seems such an obvious thing to test, however, it took
me a whole month just to get this far - there were so many candidates
to eliminate at the beginning (e.g I assumed it was something in the
dynamic page content at first). Also, it takes longer to determine a
negative result - essentially 8 hours of error-free running up to the
developer time out.
So, in summary, it now seems that any plugin call made from On Web
Connection will cause the host to fail when de-referencing a pointer
after about 800,000 to 1.5 million iterations, which in practice is
looking like 2 days of serving for me.
I think the next step may be to try to strip out everything except the
plugin call and some way to fire On Web Connection without an external
source. They only way I've done this before is using an NTK http
client to call the localhost loopback address. Any simpler suggestions ?
Regards
Peter
On 18 Oct 2010, at 01:00, Aparajita Fishman wrote:
Whew! On the one hand I'm relieved that the problem isn't with
Active4D, on the other hand this may be very difficult for 4D to
debug, and then you have to wait for a hotfix release.
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
