-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Concurrent block/item color registration causes crash #59
Comments
I am pretty sure this crash is not caused by ModernFix. One or more mods are incorrectly registering block/item colors on a background thread instead of the main thread like they are supposed to. ModernFix makes this crash more likely to occur because there is less unnecessary work being done on startup, and so more mods have the opportunity to be doing this concurrently. But I think it can happen without it as well. One solution I will probably implement from my end is adding hooks into the vanilla code to allow mods to do this safely, since there are many out there that have this problem. @Asek3 I think synchronizing access to the map in Relevant issue: Someone-Else-Was-Taken/Periodic-Table-Reforged#71 |
Correction: I already fixed this for vanilla, the fix just doesn't seem to apply to Rubidium's version of the code because I didn't anticipate it being an issue. Should be a simple patch on my end. |
I think this beta should fix your problem. This will be included in the next release. |
Hey, that fixed that issue! Thanks for the quick response and fixing it even though it isn't really caused by your mod. |
Thanks, fixed. |
So, is my interaction in Rubidium still needed? I mean compatibility with other mods maybe, not only ModernFix |
I would suggest you make that map thread-safe, as otherwise modders will likely blame Rubidium since the crash happens within its mixin. But this is really a problem with other mods for calling this off the client thread in the first place. |
The modpack loaded up now! thanks! And I gotta say absolute awesome mod. It cut down loading times from 200 seconds to 100 seconds. Keep it going. |
Thanks for the kind words. The latest release should also include this fix now. |
Describe the Crash
Added this mod to the modpack I'm working on is giving me this crash on Startup, it happens with different mods on each startup. (Once EvilCraft, once EvilCraft and Intergrated Dynamics and once AutoRegLib), without this mod the modpack works and doesn't crash. It seems to be happening on update checking. I've tried to add mods one by one (which I suspected to may cause this (mainly performance mods and mods they interact with)) without success.
Screenshots
Crash Report / log
latest.log
crash-2023-04-19_20.29.17-fml.txt
The text was updated successfully, but these errors were encountered: