Change Details

* Prepare for a pre-parse/skip tun using specific steps (below). There are currently just over 20,000 articles in the list * Start **What happens?**: Process eventually throws an OOM error, with (on an x86 box) 1.5GB memory used. This happens on AWB 6.4.0.0 and 6.5.0.0. **What should have happened instead?**: Process ends without significant memory loss. This happens on AWB 6.3.1.1 **Software version** (on `Special:Version` page; skip for WMF-hosted wikis like Wikipedia): Windows 7 and 11. .NET framework 4.5.2 to 4.8.1 give the same result. A simple app using ListBox with repeated single-item deletions does not leak. **Other information** (browser name/version, screenshots, etc.): Theories: it could be a true memory leak, for example with an IDisposable object that doesn't release its unmanaged resources. Or there could be another list of Articles that's not getting trucated. Investigating the checkins between 12633 (6.3.1.1) and 12927 (6.4.0.0) to look where the repro starts.

* Prepare for a pre-parse/skip tun using specific steps (below). There are currently just over 20,000 articles in the list * Start **What happens?**: Process eventually throws an OOM error, with (on an x86 box) 1.5GB memory used. This happens on AWB 6.4.0.0 and 6.5.0.0. **What should have happened instead?**: Process ends without significant memory loss. This happens on AWB 6.3.1.1. **Software version** (on `Special:Version` page; skip for WMF-hosted wikis like Wikipedia): Windows 7 and 11. .NET framework 4.5.2 to 4.8.1 give the same result. A simple app using ListBox with repeated single-item deletions does not leak. **Other information** (browser name/version, screenshots, etc.): Theories: it could be a true memory leak, for example with an IDisposable object that doesn't release its unmanaged resources. Or there could be another list of Articles that's not getting trucated. Investigating the checkins between 12633 (6.3.1.1) and 12927 (6.4.0.0) to look where the repro starts.

* Prepare for a pre-parse/skip tun using specific steps (below). There are currently just over 20,000 articles in the list * Start **What happens?**: Process eventually throws an OOM error, with (on an x86 box) 1.5GB memory used. This happens on AWB 6.4.0.0 and 6.5.0.0. **What should have happened instead?**: Process ends without significant memory loss. This happens on AWB 6.3.1.1. **Software version** (on `Special:Version` page; skip for WMF-hosted wikis like Wikipedia): Windows 7 and 11. .NET framework 4.5.2 to 4.8.1 give the same result. A simple app using ListBox with repeated single-item deletions does not leak. **Other information** (browser name/version, screenshots, etc.): Theories: it could be a true memory leak, for example with an IDisposable object that doesn't release its unmanaged resources. Or there could be another list of Articles that's not getting trucated. Investigating the checkins between 12633 (6.3.1.1) and 12927 (6.4.0.0) to look where the repro starts.