I don't have an answer, but I have been noticed this bug for quite a while.
It seems to be stuck at loading certain local resources for no reason (and it would eventually load, albeit took 10+ seconds):
![show slow loading](https://i.stack.imgur.com/CdTGX.png)
And during the whole time, nothing is rendered on the page (totally blank).
- It does not happen with Firefox.
- It does not happen if you simply host it on any localhost server.
The weird thing about this bug is that it isn't caused by any single resource or html element; once you reduced the elements on the HTML to a degree, it will suddenly start to work.
That's why the above answers were able to "fix" it by randomly remove something.
If you try to reduce an HTML file to find a minimum reproducible example, you will realize there are multiple ways to make it work (mostly by removing some JS, but sometimes removing some tag would also do the trick); there is no single culprit.
I personally think it's some part of the rendering process of Chrome doesn't work well with file:// protocol (probably due to lack of testing) and it's not exposed to dev tool well to tell/debug.
I have reported it on bugs.chromium.org but sadly no response yet.