Daniel ChengOn Wednesday, I tried a simple change to delete some NaCl-related code. Two days later, I've determined that I can't delete it after all, and I now know more about shared memory than I ever wanted to.
thakis@z as in it's nacl-related but also used by something else?
@thakis When creating a shared memory region on Windows, Chrome aligns requested sizes up to the nearest 64k boundary. A TODO claims the extra alignment is only needed for NaCl. But when removed, a bunch of tests fail. It turns out that v8's heap sandbox also enforces this alignment with CHECKs, since 64k is the allocator granularity on Windows. It might be possible to relax v8's CHECKs… but the "simple cleanup" has turned into a far bigger task than I was planning.
dana 
@z A perfect example of hyrum’s law.