-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
[Bug] Millennium requires opening up Steam twice to start successfully #149
Comments
I've seemingly fixed this, it will be in the latest update. Steam added something in the newest beta that causes this. I'll leave this open until I'm confident its fixed. |
I can confirm I am having this issue too. This is also occurring occasionally on the stable branch, and it can also happen with the default theme. |
Try using this version, see if it fixes it. Extract the files in your steam folder and replace all (make sure Steam is closed) |
Seems like it's fixed after trying the version from the nightly link. Restarts also seem to work properly now, including the default and other themes. |
Perfect; after some more slight bug testing I'll release that version. You can use that version as normal in the time being ofc. |
I found that after starting Windows for a period of time, Steam can start successfully in one go. If you run Steam right after starting Windows, you will need to run it twice. |
Fixed in the latest release! |
I have updated to 2.13.0, but there is still this issue |
Issue is still happening after updating to 2.13.0 on Windows. |
@NathanL1370 start steam with -dev and share the console output. Btw I thought you said the nightly link fixed your issue? |
@YCZ01111 @NathanL1370 give this a try. Just extract and replace in the steam folder |
Console output now throws a system error in v2.13.0, with the |
@shdwmtr Forgot to include this screenshot, but when I tried using your compiled version of Millennium, the console output warns that it's "upgrading" from 2.13.1 to 2.13.0, which still has the bug. (Technically, wouldn't it be downgrading in this case?) |
Ah oopsies, it's downloading the live version. Set |
I seem to be able to reproduce it, its because you have a large amount of files in your steamui folder in steam that slows down Millenniums start process resulting in a race condition. Where it says connected to SharedJSContext in 7000 ms it should be 1-2 ms |
It seems I wasn't properly freeing a thread. This should fix it https://github.com/SteamClientHomebrew/Millennium/actions/runs/11654025051 |
That was my actual issue upon further inspection in my steamui folder, it seems I had a bunch of skin backup folders that were probably created in a very old version of Millennium. |
try restoring those files to see if it works even with them in there now (if you havent deleted them permanently) |
Perfect! I plan to move skins outside of the steamui folder in the future because Steam pre-caches everything in the folder which takes a long time (happens with or without Millennium), but that's an issue for another time. |
Before Reporting
Describe the Bug
Been using v2.12.4 for a while and I find I need to start up Steam twice for it to open properly as the first time it crashes or doesn't show any Steam windows.
Below is the
-dev
console when Steam is run for the first time, something about aPromise already satisfied
Expected Behavior
Start up Steam
See login screen and then Steam window the first time
Steps To Reproduce
Windows 11, with Inject JavaScript and Inject StyleSheets enabled, and these themes/skins:
Operating System
Windows
Anything else?
No response
The text was updated successfully, but these errors were encountered: