thread/socket behvior

[Jeff Polakow]

Hello,

> I'll be interested to know if the fix helps your application.  The bug 
> reported in #2703 results in the program just allocating memory 
endlessly 
> until it dies, so it doesn't sound exactly like the symptoms you were 
> originally describing.
> 
We are currently using GHC-6.8.3 so we can't try the fixed version. We'll 
switch to 6.10 after it becomes the stable release and (hopefully) minimal 
work needs to be done to get everything to compile. This bug actually 
perfectly explains the behavior we saw in our full system. 

The distilled test case we reported was based on our then current theory 
that too many connections were the cause of our problem. We're pretty sure 
the behavior we described was real, but it was not the cause of our 
problem as subsequent testing revealed. After delving deeper, we realized 
that the real culprit was too much data over one connection. 

-Jeff


---

This e-mail may contain confidential and/or privileged information. If you 
are not the intended recipient (or have received this e-mail in error) 
please notify the sender immediately and destroy this e-mail. Any 
unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.haskell.org/pipermail/glasgow-haskell-users/attachments/20081022/f0fcc98b/attachment.htm