#6 Resource leakage under Win95

[Paul Sokolovsky]

Under Win95, running configure long enough (10+ times) leads to inability to run processes any more. Closing console window of such session helps a bit (for one more configure session), but only reboot restores system's state.

[Paul Sokolovsky]

Typical configure session includes running hundreds of processes (about 2000 for textutils-1.22). Each process starts (additional) thread for interprocess signal watching. It is known that under Win95 starting thread leads to memory leak (ref: MySQL win32 port). Probably, running thousands threads really puts fatal strain on win95. This is only a hypothesis currently.

[Paul Sokolovsky]

It seems that NT systems also suspectible to this problem. However, they manifest another behaviour - for example, after long run of configure/regression testsuite under win2000, its taskbar was gone (but it was possible to continue running PW32 processes). Well, I don't know from what to start hunting this issue, so for 0.6.0 I'll try to use workarounf - some often-run commands will be build without interprocess signalling support (and hence, separate running thread). We'll whether that wil change something.