On Thu, Nov 10, 2022 at 01:53:25PM -0800, Ives van Hoorne wrote:
I verified these latest changes with my initial test case, and can confirm that I haven't been able to reproduce the problem anymore! Usually, I would be able to reproduce the error after ~1-5 runs, given that I would fill the page cache before the run, now I have been running the same test case for 50+ times, and I haven't seen the error anymore.
Thanks again Peter for taking the time to find the issue and coming up with a fix!
Thanks for the quick feedback, Ives!