> We too do not have any databases > involved with this app, but sockets--you bet. It's LAN messaging, so > sockets are what it's all about! In any case, I wanted to let you know that > I'm working with my customer to figure this out and will fill you in on anything I > learn. So far, it's just one XP machine that we see this on. I'd love to hear > what you are able to understand about this, too.
Here is what it looks like so far. In the original code, that did not produce the memory error, we were using a timer as part of the parsing routine. The socket DataAvailable event would append any incoming data to a string. Then a timer would look at the buffer to see if the buffer contained an end-of-packet character. It would then parse the packet. This works, but is slow when receiving large amounts of data. To help speed things up. The code that checked for the EOT character, and then handled the message, was put into the DataAvailable event. This is much faster, but it appears to be what is triggering the memory error. When the packet handler was placed back into a timer, the error stopped occuring on the one in-house test machine where it was happening. I haven't had a chance to test it at the customers site yet. --Seth -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
