| Ticket UUID: | 1056311 | ||
| Title: | async-4.3: huge memory hog | ||
| Type: | Bug | Created on: | 2004-10-28 18:41:28 |
| Submitter: | dgp | Assigned to: | mistachkin |
| Subsystem: | 04. Async Events | Severity: | |
| Priority: | 5 Medium | Last modified: | 2026-10-22 17:19:27 |
| Status: | Closed | Closed by: | serhiy.storchaka |
| Resolution: | Fixed | Closed on: | 2026-10-19 11:58:16 |
| Version: | 9.0.5, 9.1.0 | ||
| Description: | ||||
The test async-4.3 consumes very large amounts of memory, and on underpowered systems can cause a `make test` to fail. | ||||
| User Comments: | ||||
dgp added on 2005-01-26 21:51:51:
Logged In: YES user_id=80530 davidw expressed interest in this issue on the chat. wliao added on 2006-10-21 02:03:24:
Logged In: YES user_id=863965 For my tests, I had to make the string repeat value smaller. The original value took so long to run and used so much memory that it masked the failure of the underlying test. mistachkin added on 2009-11-02 12:22:12:
This bug is not a duplicate of 1774689; however, they are related and will both be fixed at the same time. This test and the underlying C code is going to need major revision(s). serhiy.storchaka added on 2026-10-17 06:24:49:
Since [c0c61fa7cf] async-4.3 runs only on MSVC builds (the knownMsvcBug constraint was inverted), so it did not use memory elsewhere; fixed in branch async-test-msvc-constraint. The memory is for compiling the 1500000 commands. With 150000 they run in 0.7 ms here, less than the 1 ms after which [testasync marklater] fires the event, so the test would no longer check the delivery inside the sequence. | ||||
