For example, I tested Google chrome 49.0.2623.112: https://www.filepuma.com/download/google_chrome_32bit_49.0.2623.112-11045/download/ and Spotify 18.104.22.168: https://www.filehorse.com/download-spotify/26140/download/. In 0.4.11-dev-852-3e3560e9c23db7ba6cbb916cfb7f42a11b650edf they worked correctly. Since 0.4.11-dev-853-6d6e3712259e06cc49b753447a8bdfe49a4eabc4, Spotify starts successfully, but after login crashes. Chrome doesn't launch at all after one double click on exe or lnk. Only after two double clicks appear processes in taskmgr and the browser window, but only for a moment. Then it disappears, and chrome.exe processes are terminated immediately. As with no-sandbox – enabled, and without it.
In google-chrome.log I see the following suspicious lines after launching Chrome:
Judging by the last line, it seems to me that https://github.com/reactos/reactos/pull/770 may (partially) fix this issue.