| Ticket UUID: | 147b28d0436d4267a3d95082339f78980144b004 | ||
| Title: | Win32 WaitForInputIdle and potentially unwanted 5 seconds delay | ||
| Type: | Bug | Created on: | 2023-05-01 17:33:13 |
| Submitter: | chw | Assigned to: | nobody |
| Subsystem: | 49. Threading | Severity: | Minor |
| Priority: | 5 Medium | Last modified: | 2023-05-02 05:54:41 |
| Status: | Open | Closed by: | nobody |
| Resolution: | None | Closed on: | |
| Version: | most likely all | ||
| Description: | ||||
See discussion on c.l.t. https://groups.google.com/g/comp.lang.tcl/c/TZ4pmzR5Js8 | ||||
| User Comments: | ||||
apnadkarni added on 2023-05-02 02:22:52:
There is a possibility that this WaitForInputIdle call is no longer needed as the Windows bug is no longer present (and has not been for a while). See https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/124121 (fixed in NT 3.5 service pack) chw added on 2023-05-02 04:32:50:
Then let us throw out this olden code from long gone times where rubber boots were made from wood. Is a TIP required? apnadkarni added on 2023-05-02 05:43:47:
I don't see why a TIP would be required. But a test to ensure the original memory leak is no longer present would be desirable. Or we could just remove it and wait till someone complains about a leak :-) chw added on 2023-05-02 05:54:41:
Well then, Ashok, given that proving there ain't no leak is most likely a very difficult task, I'd prefer the latter option, i.e. postpone problems to the Complaints Department which anyways is the most profitable division of the Sirius Cybernetics Corporation :-) | ||||