You didn’t hit the page file. This is OPFS, an in-browser filesystem that is sandboxed to each origin (essentially to each website), not directly accessible by the user, and exempt from the security checks that would guard access to the regular filesystem.
Yeah, that sounds to me like it needs a major revision.
You don’t download the file. The JavaScript generates the file right on disk.
Ah that makes more sense. Seems like something easy to detect at least.
It’s been a while but doesn’t Windows let you know when you exceed RAM usage and hit paging file?
You didn’t hit the page file. This is OPFS, an in-browser filesystem that is sandboxed to each origin (essentially to each website), not directly accessible by the user, and exempt from the security checks that would guard access to the regular filesystem.
Yeah, that sounds to me like it needs a major revision.
but in order for the file to use all available RAM, other processes that still need memory will eventually trigger the out of memory warning… no?
unless I’m completely misunderstanding and OPFS has a set limit of RAM usage before it automatically starts writing to drives.