[Issue Tracker] "The engine did not get ready within engine startup timeout!" #166
Comments
|
UnityWebBrowser.Engine.Cef.log Error 1 - [Web Browser]: The engine did not get ready within engine startup timeout! Try increasing your 'Engine Startup Timeout' time. If you continue to have this error, see issue report #166 on GitHub. Warning - [Web Browser]: [Engine]: No communication layer provided, using default TCP... I DONT KNOW WHY IS IT GIVING THIS WARNING BEACAUSE tcp FILE IS ATTACHED ON SCRIPT AND ( THERE ARE TWO WAY TO FIX IT ONE TO CLEAR CACHE ON TASK MANAGER AND SOMETIMES IT DOES NOT SHOW UP IN THERE SOI CHANGE THE tcp PORT AND IT WORKS FOR FOR FEW MINUTES ) KINDLY HELP ME OUT WITH THIS OS is window 10 |
|
Looking at the CEF logs, it appears the cache is still locked by an another UWB process, meaning that the CEF process is not shutting down correctly for some reason... Try disabling the cache in Client settings.
If your communication layer is set to TCP, then this debug log message is expected. |
|
I tried disabling the cache as well but still having the same issue, |
|
I have the same problem, restarting the computer helps. Is there another solution to the problem? |
|
I set the timeout to much longer and this seems to have resolved the issue. CEF itself is perhaps a bit of a resource hog which probably explains why it takes a bit long to start! Given this, it may make sense to increase the default startup timeout. |
|
another start error [Web Browser]: [Engine]: Error setting up IPC! |
This error has nothing to do with this issue. |
|
I am getting this error: I disabled the cache and set my timeout to Other Logs: |
|
@Voltstro everyone on my team has encountered the issue @jacobbullock is having. Seeing as it’s a blocker to what we’re doing we’re very motivated to figure it out. Is there something else we can provide to be helpful here? Maybe jump on a call so you can see what we’re encountering live? |
|
Just to add a further follow up, the issue is still occurring on a somewhat regular basis, even after trying all the suggestions (including mine). By the way, if anything this issue seems to be worse after updating to the latest release. I'd further add that disabling the cache is a poor solution at best, as it tends to push responsiveness from barely acceptable to simply awful! |
|
I think I finally, really, figured this out! The issue is caused by "Graphics APIs for Windows" set to "Direct3D12" in "Player" settings. I've set to only "Direct3D11" which is now working well! |
|
I updated to use Direct3D11 today and that didn't seem to fix it for me. I am noticing something very strange though. If I restart my laptop, I am able to open unity and work on the app and have the browser work without any issue for what seems like 25-30 minutes. Making some code changes, running the app, over and over. After about 30 minutes the browser stops working. I've tried quitting just unity and that doesn't seem to fix it. I have to restart my whole computer and I can work with the browser again. Is it possible there is something being left behind in memory when quitting the app and rebuilding? |
|
I've been taking a look into this. I think I have reproducible steps now.
From here, you can see that the UWB Engine process is still running in the background, with the ports bounded. Normally UWB will send a shutdown signal to the engine process, and even if it doesn't shutdown in time, UWB will force kill it. But with either a domain reload or a force close, UWB doesn't get a chance to do that. I really see three issues that need be fixed here.
|
|
Release 2.1.1 includes fixes to potentially resolve this issue. Please update and see if you can get the issue to occur. (Ensure that no UWB Engine process is running in the background) |
|
I've now implemented the latest release and confirm that it works and seems more stable than the previous release. In preliminary testing I found no issues with any UWB engine processes lingering. I have not yet completed extensive testing for the original issue but have not encountered the timeout error so far! |
|
We have not seen the engine timeout issue at all with |
|
No one has reported this issue in three months. Closing as completed. |
|
Premise that last week was working perfectly Log: Error: |
Tracker
We are using this issue to track this error: "The engine did not get ready within engine startup timeout!".
Issue
We have been getting a lot of reports of UWB not starting, and spitting the above error message out. We've yet to reproduce this issue on our end, so we are creating this issue to track all reports of the error.
Report
If you are having this issue, try these steps first:
LibraryFolderIf you have tried these steps, then move onto providing us an issue report HERE (in the comments on this issue).
Start by getting the error message:
Once you have the error, provide these details in a comment on this issue:
Provide us ALL log messages in the console for this session where the error occurred. DO NOT JUST PROVIDE A PICTURE OF YOUR CONSOLE, provide it in text format with the stack traces, and put everything in GitHub's markdown code blocks so it is easy to read. If you want an easy way to copy it, go to your Unity editor log file, and copy the text for the error's session from there.
There is a second log file created at
Library/UnityWebBrowser.Engine.Cef.log. Please also attach this log file.What Platform (OS) you are using, and your Unity editor version.
The text was updated successfully, but these errors were encountered: