* Jörg F. Wittenberger <[email protected]> [130309 12:26]: > I'm afraid I have no idea how I could boil this down to a reproducible > case. > > I've seen it once so far in a logfile of a process, which xreates > approximately 2000000 threads a day when communicating over WAN > with about ten peers plus all those public web access (approx. > since chicken does not have unique thread numbers, but rscheme > does; when I run the rscheme version instead I see thos 2^6 threads; > though the chicken version has a different runtime behavior and does > not share 100% of the code, hence it could use a different amount of > threads.) >
I am confused. I thought you were wondering about a compilation message you get during the flow analysis of the scrutinizer. And ripping out the offending definition with the corresponding code paths from your (include)'d file was what I was asking for. I fail to see how your runtime behaviour has any influence on that phenomenon. Still I don't want to question your judgement as I don't know the code. However I doubt that we are of much help without precise descriptions of what's actually happening. Without code this is highly improbable to be useful. I am sorry, Christian -- In the world, there is nothing more submissive and weak than water. Yet for attacking that which is hard and strong, nothing can surpass it. --- Lao Tzu _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
