[mort96]

The reasons browsers rely on overcommit has nothing to do with them failing to release memory back to the OS properly.

[LoganDark]

If the memory is never released back to the OS after it is done being used (or when it is not going to be used), then the browser has failed to release it back to the OS.

[mort96]

The memory is released back to the OS after it is done being used.

[LoganDark]

If that were the case my OS would not crash due to tens of gigabytes of allocated-but-not-used memory from Firefox