I was able to launch/package this project for chrome on 10/24 and it worked fine. downloaded 4.14 preview and tried testing some things out on a blank project and it crashed my computer. Tried running 4.13 with a blank and launching in chrome and will crash about halfway through compiling. Now nothing will launch in Chrome and only .
Hi ,
- What version of chrome are you currently using?
- Does this occur in a clean, blank project with no additional content or is it limited to one project?
- What steps can I take to reproduce this error on my end?
Hi ,
I am using version 54.0.2840.71 m (64-bit) of Chrome, and 52.0a1 (2016-10-25)(64-bit) of .
It occurs with all of my projects, including a clean blank project with no starter content. it makes it to the “UE4Game.js Downloaded” in chrome before crashes.
It only stopped working once I installed 4.14 preview and tried launching a blank project to chrome from that version, which crashed my computer. Going back to 4.13 did not resolve the issue. I uninstalled all version of UE4 and VS2015 and reinstalled them. Reinstalled the latest version of Emscripten. Also cleaned the registry, but it still only runs in . Unfortunately, I would like this running in Chrome.
Thanks,
While I was able to reproduce this in 4.14, I was unable to see any error when loading an HTML5 game in 4.13.2. Have you tried 4.13.2 to see if the error occurs there or are you currently using 4.13.1?
I was using 4.13.1 this morning. When I uninstalled all versions, I installed 4.13.2 over 4.13.1 and the problem still persists.
Are you on Windows, Mac, or Linux? Unfortunately, I have not been able to reproduce this on my end.
I’m running Windows 7 Professional w/ SP1 64-bit.
I’m looking at the output log and its showing a fatal error.
"Fatal error in c:\b\build\slave\win64-pgo\build\src\v8\src\runtime\runtime-internal.cc, line 333
Check failed: size <= Page::kMaxRegularHeapObjectSize."
Is that something that can be addressed? or is there a crash log that might help with troubleshooting?
Try using Chromium, it is specifically designed for HTML5. You can find more information on it here:
Hi ,
We have not heard from you in several days. I am marking this as answered for tracking purposes. If you are still experiencing this error, please comment with the requested information.
We’re experiencing this same error (UE 4.13.2, Chrome 54.0.2840.71 m (64-bit), Win7 x64 w/SP1), using a new empty C++ project.
Launches fine in Chromium and Firefox.
In Chrome, the loading bar progress function isn’t able to correctly track the remaining download. (Logs the “weird, couldn’t get size” message). It finishes at around 25% download completion (after UE4Game.js downloaded) and begins compiling. Using Chrome’s Task Manager, I can see during compilation that the tab’s memory usage rapidly approaches around 1.3 GB, whereupon the tab crashes and the error:
Fatal error in c:\b\build\slave\win64-pgo\build\src\v8\src\runtime\runtime-internal.cc, line 333
Check failed: size <= Page::kMaxRegularHeapObjectSize.
is thrown in the output log.
This looks like a problem with Chrome, as our UE 4.12.5 project also no longer works on Chrome.
Hi .madden,
Unfortunately I have not been able to reproduce this on my end. Here is what I did:
- Open Editor (c++ blank project with no starter content)
- Launch>Chrome
At this point, I was able to launch the project on Chrome without any issues. Do you have any other steps that can be taken to reproduce this on our end?
Weird, I didn’t get an email notification about this.Testing now, but I don’t think there’s anything else I did…
Same deal.
- Open Editor (4.13.2, C++ blank project, Mobile optimized, 2d/3d scalable, no starter content)
- Launch->Chrome
- Same issue as above.
Going to try 4.12.5 again shortly.
This also happens in 4.12.5 with the same steps.
.Madden,
I have packaged a C++ blank project from 4.13.2 and launched it onto without any trouble. I’m on 53.0a1 (2016-11-21) (64-bit).
I tested in 4.14.0 too.
Hope this helps.
The problem is only in Chrome (54.0.2840.71). Firefox, , and Chromium work fine.
This shouldn’t be an issue if you upgrade to Chrome 54.0.2840.99 m (64-bit) or later.
Seems to be working now in 54.0.2840.99 m
Awesome, thanks for the update!