-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.6.0 fatal error on launch #1178
Comments
Please share a diagnostic report from Help > Upload Diagnostics or |
|
drats - now when I try to install the stable version I then get a different error... So I deleted (renamed) ~/.orbstack, downloaded stable version, launched it, worked, upgraded to canary and it launched with no issue. So the problem with ugprading is somewhere in my .orbstack folder :) Hope that helps. |
It's the memory size. Will fix but in the meantime it should work if you set it to ~60GB or less. |
No worries. |
Fixed for the next canary. |
Awesome - thanks. |
Released in v1.6.0 Canary 2. |
Upgraded... no further issues - thanks again. |
Thanks - had for the last few days a few issues with your internal networking but not mentioned it as I cannot replicate each time, I hope its not a bug but I think it might be. *.orb.local domains seem to be routing to different services or ports - hard to replicate to give you any detail at this stage, but orb stop/start and then docker-compose up again seems to fix it. This only started in the canary for 1.6. Not had it yet on 1.6.0 as released so will keep an eye on it (unfortunately I switch projects a lot during the day haha) |
Known issue, will fix in the next version. |
ah man you are a star! I did not want to mention the issue until I had rock solid proof of concept to replicate it for you. Awesome. I'll stop trying to replicate it for now then, and will be patient for the next version. |
Describe the bug
Saw your tweets, upgraded to 1.6.0, started Orbstack - got "Stopped unexpectedly: fatal error"
To Reproduce
upgraded to 1.6.0, started Orbstack
Expected behavior
no error :)
Diagnostic report (REQUIRED)
Screenshots and additional context (optional)
The text was updated successfully, but these errors were encountered: