Jump to content

Bartdoytr22

Members
  • Posts

    13
  • Joined

  • Last visited

Bartdoytr22's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. Just tested, I lowered render distance and it still froze within 30 minutes of gameplay.
  2. I have tried most of the methods, however, only one method worked, which was using jconsole for the thread dump. However, once the freeze happened and I tried to inspect the threads, the threads won't update and show their current state, which meant that it didn't allow me to view the current threads. All the graphs and stuff were frozen and everything would just stop completely. Though, I was able to still look through the threads, and when the crash happened, it was on an IO-Worker thread. I don't think this was the cause of the freeze, but it was the last thread in the list when the freeze happened. I tried it again and a different thread, called Thread-222 was the most recent in the list. Before that, it was another IO-Worker thread. I think this crash might just be a hardware issue with saving sometimes, possibly with not having enough RAM to run this ginormous conglomerate of a modpack. I am running 16 gigabytes with only 24 gigabytes of RAM, so maybe it might just be not having enough memory. I might just need to lower my render distance, since currently I have currently set it to 15 or 18, which is probably way too high for this kind of modpack.
  3. To answer the stuff that you offered: I have no idea how to start any of those ways to do a thread dump, since I have literally 0 knowledge of the Java programming language and running the Java console and all that. I would love to have help starting that stuff. That's what I'm theorizing. It's likely that a mod is failing to save something, or the save size is probably so large that the game was not able to handle it. In my experience, CarryOn is a relatively stable mod if you are quite careful with it. The only reason I included it in the post is because it was easy to describe, and it just happened to me right before I created the post.
  4. I have had task manager opened when the issue occurred, and it seems to say that it's "Suspended." I checked my memory, and it says I have 7 gigabytes left. To give some context, I am running Minecraft with 16 gigabytes maximum RAM and my PC has 24 gigabytes. I doubt it's a memory or hardware issue. To answer your questions, I choose to not run Optifine due to the incompatibility with multiple mods, so I am using Rubidium alongside a myriad of performance mods. I am running the game as a local world. I believe it is somewhat of a mod issue and a little bit of a hardware issue, as further testing showed that the crash mostly happens when I unpause and pause within a short time. This frequent pausing might have interfered with the saving, which being there many dimensions and stuff in the dimensions, would take probably many milliseconds longer. Once you unpause and pause it again, it starts saving again, causing the freeze since the game doesn't know what to do. This might explain the saving issue. However, I am not a modder myself, nor a person who really understands Minecraft's coding landscape, so this is just a mock-up theory to what might be happening. Also, the only reason I think the saving has a problem is because the logs normally cut off when the game is saving dimensions.
  5. The game window does not respond at all, Windows knows that it isn't responding when I click on it while it's unresponsive. The background of the game does still render, but I can't unpause because the actual game window doesn't respond.
  6. Playing on a modified ATM 8 modpack. Forge 43.2.8 Minecraft freezes completely when pausing the game. However, this only happens sometimes, but it's impossible to exit out of it without completely exiting out of the game. The odd thing is whenever I try to reload it back up, the world itself is in a partially saved state, where everything in my inventory did save right before the freeze, but the world itself did not fully save, so for example if I was to be carrying a chest using the CarryOn mod and my game froze on the pause screen and reload it back up, I would still be carrying the chest, however the chest in the actual world would still be there. Basically duplicating the chest. This might have given a hint to what the problem is, however looking at the log showed no trace to what the problem is or how it could be solved. Here is my log, and the mod list if it helps at all. https://gist.github.com/vainlaind4in/f1a49f41e48f084169b6b9104c5a7fa3
  7. Oh my goodness! Thank you so much for tracking down the mod for me! I have had trouble with this for over 3-4 months and I haven't found the mod, and you took the time to find it out. Thank you.
  8. Playing on a modified ATM 8 modpack. (I finally got it working!) In the modpack that I am playing, whenever I have anything in my main hand, it applies an NBT tag, which shows only as {} when I try to see the NBT using advanced tooltips. Once you place and break it (if it's a block) and pick it back up or drop it and pick it up again, it removes the tag, which causes stacking issues. I can confirm that this does not happen on the original ATM 8 modpack, and it only occurs in my modified one which has mods that I have added. I do not at all know what mod that I have added is causing this anomaly. It really makes this modpack awful to play, and I'm just trying to find help. Bigger Stacks is not the culprit, as I already tested it without it and the problem persists. Here is the full mod list:
  9. As I was making that reply, it appeared that if you just revert to the previous version for S. Core, S. Backpacks, and S. Storage, the game does boot up normally.
  10. As I've said, I have posted an issue on the Bigger Stacks issue tracker, so hopefully they're going to fix it sometime soon. I'll go into the Sophisticated Storage issue tracker as well. It does appear that the latest version of Sophisticated Core has changed some stuff which did broke compatibility between the 2 mods.
  11. Crashing once again. However, this time, I think Forge crashed somehow because a bunch of other mods are included in the crash that only seem to be listed because they failed to load. Also, instead of crashing during the loading, it crashes a couple seconds after I launch Minecraft. It seems strange, but the only cause I can see from this is by removing Sophisticated Backpacks, but that errors when Minecraft is loading because of the Bigger Stacks mod (I posted an issue on the Bigger Stacks tracker.) I forgot what I added, but it's definitely breaking this modpack. Forge 43.2.8 Crash report: https://gist.github.com/vainlaind4in/14255807238012f0833a2fda0c007206 Log: https://gist.github.com/vainlaind4in/f1257c05bd170b9066d3ab3354fd8545
  12. Oh, right. I found a different person reporting the same issue on their GitHub just now, so I can hopefully find a fix for it. Thanks for finding it and narrowing it down for me.
  13. Using forge 43.2.6. Using ATM 8 modpack with my own mods and my own configurations. Once the game is started up to the loading screen, the loading screen is corrupted with purple and black squares. Something, somehow broke ATM's custom loading screen. After a little bit, the game outright crashes with this report: https://gist.github.com/vainlaind4in/45aaa50c7cf632d361249c8515704d51 Here is the latest.log, if it'll help: https://gist.github.com/vainlaind4in/ee86d41dc03c2866275fa3264875a118 I've tried to look through the latest.log and the crash report to find the issue myself, but I could not find any specific mods that were causing it, and I am not a coder myself. I'm thinking it's something to do with a mod that changes rendering, or an obscure mod incompatibility.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.