That shouldn’t happen normally, but there are a couple different things that can cause it. First, the new editor uses the REST API so the first thing to check is to see if that is working. Sometimes a web server configuration (either made by the site owner or the host) is blocking the API inadvertently or as a very strict security rule they block everything API related which breaks some functionality as things get updated. Another possibility is a conflict from a plugin, most commonly a security plugin.
The first thing for you to check is whether your API is working. You can do that by adding /wp-json/after your domain. If you see a bunch of text, that is good. If you see an error, you will need to figure out why it’s there and find out how to make sure your API is working.
If that doesn’t solve the problem, I would suggest temporarily deactivating any plugins that you think might be the source of the trouble and test again. If the editor starts working, turn each plugin back on one by one. If you do find a plugin conflict and can note it here, I can help you find the information that would most help the plugin author in getting the conflict fixed.
One place to look for errors which may help provide a clue for the problem would be to check the console in your browser’s web developer tools when you see the blank page. Sometimes an error will be listed there that can help uncover the problem.
Last, here is a list of similar cases that have been solved already and one of them may help you but if that looks overwhelming then check the suggestions above first and reply with what you find.
https://github.com/WordPress/gutenberg/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed++solved+in%3Atitle+
