| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
A test which really allocates the memory it asks for (that is, run with -M) now runs in a subprocess, so that the memory it uses and the address space it fragments are released when it ends. A dummy run stays in the process. The parent process watches the memory usage of the subprocess while waiting for it, so the separate watchdog process is no longer needed. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14, 3.15. |
Sorry, something went wrong.
|
Sorry, @serhiy-storchaka, I could not cleanly backport this to 3.15 due to a conflict. cherry_picker 66d7c891044915ccb7a12e0cc2c78991508e816e 3.15 |
Sorry, something went wrong.
|
Sorry, @serhiy-storchaka, I could not cleanly backport this to 3.14 due to a conflict. cherry_picker 66d7c891044915ccb7a12e0cc2c78991508e816e 3.14 |
Sorry, something went wrong.
|
Sorry, @serhiy-storchaka, I could not cleanly backport this to 3.13 due to a conflict. cherry_picker 66d7c891044915ccb7a12e0cc2c78991508e816e 3.13 |
Sorry, something went wrong.
|
GH-156013 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
|
GH-156014 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
|
@serhiy-storchaka, |
Sorry, something went wrong.
|
Backporting to 3.15 needs merging several other backports first. |
Sorry, something went wrong.
A test which really allocates the memory it asks for (that is, run with -M) now runs in a subprocess, so that the memory it uses and the address space it fragments are released when it ends. A dummy run stays in the process. The separate watchdog process is no longer used. Unlike in the main branch, the parent process does not report the memory usage of the subprocess: get_process_memory_usage() (gh-150114) is not available on this branch. (cherry picked from commit 66d7c89)
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.15. |
Sorry, something went wrong.
|
Sorry, @serhiy-storchaka, I could not cleanly backport this to 3.15 due to a conflict. Please backport manually with cherry_picker, see the devguide for more information. cherry_picker 66d7c891044915ccb7a12e0cc2c78991508e816e 3.15 |
Sorry, something went wrong.
) A test which really allocates the memory it asks for (that is, run with -M) now runs in a subprocess, so that the memory it uses and the address space it fragments are released when it ends. A dummy run stays in the process. The separate watchdog process is no longer used. Unlike in the main branch, the parent process does not report the memory usage of the subprocess: get_process_memory_usage() (gh-150114) is not available on this branch. (cherry picked from commit 66d7c89)
|
GH-159087 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
) A test which really allocates the memory it asks for (that is, run with -M) now runs in a subprocess, so that the memory it uses and the address space it fragments are released when it ends. A dummy run stays in the process. The separate watchdog process is no longer used. Unlike in the main branch, the parent process does not report the memory usage of the subprocess: get_process_memory_usage() (gh-150114) is not available on this branch. (cherry picked from commit 66d7c89) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
| Back | FazBrowse Home | New Git URL |
A test which really allocates the memory it asks for (that is, run with -M) now runs in a subprocess, so that the memory it uses and the address space it fragments are released when it ends. A dummy run stays in the process.
The parent process watches the memory usage of the subprocess while waiting for it, so Lib/test/memory_watchdog.py and the separate watchdog process are no longer needed. _SubprocessTest.wait() calls back every second between communicate() timeouts, which does not lose the subprocess output.
Tested with -M 4G and -M 20G on Linux, and with -M 4G on FreeBSD and on a Windows debug build.