Deadlock when launching more than 75 tasks

[Silvertail4764]

Description

Ever since I updated to 4.7.1, its been stuck on "Checking for Compatible Updates" Ive tried reinstalling, disabling firewall, and resetting the config, Im at a loss

Steps to reproduce

Run Ferium Upgrade
It get stucks at Checking for Compatible Versions

Operating System

Windows

Are you using the latest version of ferium?

• I am using the latest version of ferium

Additional Information

If you need any more info, Ill be happy to provide

[theRookieCoder]

Can you check with the previous version of ferium to see if the same error happens. Also your terminal seems to running as administrator, is that intended?

[Silvertail4764]

Yes Im running as admin as intended.
I downgraded to version 4.7.0 GNU and everything works completely fine.

[theRookieCoder]

You're using the GNU versions on Windows? Can you test it in mingw (or whatever you're using) directly instead of powershell.

[Silvertail4764]

Ive tried the gnu & msvc versions of 4.7.1 through PowerShell and no luck. Idk how to install the gui version on Windows, apologies for inconveniences

[theRookieCoder]

Could you send me your profile. If you want to send it privately you can contact me on Discord at @therookiecoder.

[Silvertail4764]

I sent my config file, or is it something else you need

…

On Thu, Sep 26, 2024, 10:18 AM Ilesh Thiada ***@***.***> wrote: Could you send me your profile. If you want to send it privately you can contact me on Discord at @theRookieCoder. — Reply to this email directly, view it on GitHub <#432 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEKEMXQFG5PCOZPWSUZH67TZYQQV3AVCNFSM6AAAAABO5FO7T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGI3DSNJZHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[theRookieCoder]

Sorry I did not receive it

[Silvertail4764]

config.json
Here is my config, lmk if it doesnt work

Edit, I installed using Winget btw, idk if thats relevant at all

[gvancamp]

I was seeing the same thing on the windows-msvc build 4.7.1. I had to revert to 4.7.0.

[Silvertail4764]

I was seeing the same thing on the windows-msvc build 4.7.1. I had to revert to 4.7.0.

At least it wasn't just me and I was being an idiot, my worse fear

[theRookieCoder]

config.json Here is my config, lmk if it doesnt work

Ok I can reproduce this bug using your profile, thank you! I did change the multithreading code in this update, I suspect there's some sort of deadlock happening.

[ivxvm]

Same on Linux (Pop!_OS 22.04 LTS x86_64) with 4.7.1, reverting to 4.7.0 fixed it.

[BilElSicario]

I was seeing the same thing on the windows-msvc build 4.7.1. I had to revert to 4.7.0.

how do you do that ?

[theRookieCoder]

I was seeing the same thing on the windows-msvc build 4.7.1. I had to revert to 4.7.0.

how do you do that ?

It depends on how you installed ferium. If it's manually by downloading from GitHub releases, then you can download the previous version and install it as usual. Otherwise it depends on your package manager.

[BilElSicario]

I was seeing the same thing on the windows-msvc build 4.7.1. I had to revert to 4.7.0.

how do you do that ?

It depends on how you installed ferium. If it's manually by downloading from GitHub releases, then you can download the previous version and install it as usual. Otherwise it depends on your package manager.

I figured it out but I have 112 mods and it stops at 98/112, maybe it's a thread problem I figured. But I don't know anything about changing environment variables or whatever.

I changed to 4.7 then 4.6 and it's still the same.

Can you give me your discord so maybe you can help me ? It's really frustrating me... Would be very much appreciated when you have time

[theRookieCoder]

My discord is therookiecoder, I might not be able to respond immediately.

[BilElSicario]

My discord is therookiecoder, I might not be able to respond immediately.

No problem, I'll add u and answer whenever you have time :)

[fengshuo2004]

I am also experiencing the same issue using Ferium 4.7.1, can confirm switching back to 4.7.0 fixed it. Maybe the update should be rolled back across package managers since it is broken?