Futurepack-API
Futurepack-API copied to clipboard
mcenderdragon
Strange pid error MC 1-18-2 Forge 40.0.52 and Futurepack 33.0.7268
A strange pid error is crashing the game. I haven't played futurepack for a while and wanted to have a look at it in MC 1-18-2. I made a pack, loaded the game, and it crashes with a pid file mention about futurepack. A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior: Attempt to load my custom made modpack and it crashes
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
Version Minecraft Version: 1-18-2 Forge Version: 40.0.52 Futurepack Version: 33.0.7268
Logs Isn't producing a crash log. https://pastebin.com/XKmYvQcn - pid log Debug is too big for pastebin https://pastebin.com/yVCuppKr - fp latest https://pastebin.com/uH2TVaZt - latest log
Try this one
https://gist.github.com/trogarus/3590ddecaa9682ecada1a9b862e6bb58
Matter of fact, it crashes the launcher. Can't even get game to fully load.
Do you use the lunacher provided java or a self installed one? if its from the launcher try a self installed java 17.
Its weird, it crashed while trying to write files to your disk. Is it always the same PID crash report? Also areoyu using and SSD, a HDD or a m2 SSD? And what about your RAM is that old are you overclocking ?
No overclocking. 16GB RAM. New SSD installed a little over a year ago. I'll double check file permissions on the folder to see if maybe those are read only.
Check your SSD drivers then, I am only guess at straws here but its something very low lever thats crashing here.
Also you should relog into the launcher as that file contains your access token
OK, just did the file permissions, will log out and back into the launcher and try again.
Just double checked paths and system stuff for Java. I already re-installed Java :) About to try another launch after ensuring proper file permissions in game folder and checking system environment. Will report back.
On the SSD drivers, why would it only happen with Futurepack? Same thing with re-installing Java. I have 178 mods in this self built pack. Logged out of launcher, logged back in. Again, if I remove futurepack, this all goes away. Pack launches. I can create worlds. I can save and rejoin worlds, but not when Futurepack is enabled. Latest logs, still no crash log.
New Pid https://gist.github.com/trogarus/29105a696b059196c4e8939597b2d5a3 New Debug https://gist.github.com/trogarus/3f6b7e8d15e67592991db25208b6a7f5 New FP-Latest https://gist.github.com/trogarus/cbb07ae8ed9900a6e3d83f67498735e7 New Latest https://gist.github.com/trogarus/ed2de44652e0e539d50a3f9ec4c01687
More testing. Built a minimalist pack with futurepack, added like 5 - 10 most common mods. No issues. So, I'm guessing this is some kind of weird mod interaction issue. Will start testing the pack I have and remove mods to try and narrow it down. Will report back.
On the SSD drivers, why would it only happen with Futurepack? Same thing with re-installing Java. I have 178 mods in this self built pack. Logged out of launcher, logged back in. Again, if I remove futurepack, this all goes away. Pack launches. I can create worlds. I can save and rejoin worlds, but not when Futurepack is enabled. Latest logs, still no crash log.
New Pid https://gist.github.com/trogarus/29105a696b059196c4e8939597b2d5a3 New Debug https://gist.github.com/trogarus/3f6b7e8d15e67592991db25208b6a7f5 New FP-Latest https://gist.github.com/trogarus/cbb07ae8ed9900a6e3d83f67498735e7 New Latest https://gist.github.com/trogarus/ed2de44652e0e539d50a3f9ec4c01687
it crashed in ntdll.dll ?! something in your system is unstable. and I have no idea why futrepack isc ausing that, its just a normal stacktrace trying to be printed. When the crash occurs is cour CPU at 100% ? Becuase my only guess right now is its load depedendant as its happening during worldgen.
Also you can try with a powershell run as administrator:
Repair-WindowsImage -Online -RestoreHealth
That should fix any windows related issues
So, spent hours enabling and disabling mods. This is what I've found.
The mods in question require: Supermartijn642's Config Library 1.0.9 Supermartijn642's Core Library 1.0.16b
Mods in question (all Supermartijn mods) Entangled 1.3.10 Packed Up 1.0.25 Scarecrow's Territory 1.1.4 Wormhole Portals 1.1.9b
Enable any of the mods in question and the crash happens. The libraries don't seem to affect anything alone.
Used the following, administration level command prompt, no errors
sfc /scannow Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /CheckHealth
The file ntdll.dll is a DLL (Dynamic Link Library) file stored in the system folder of Windows operating system. It is usually created automatically during the installation of the Windows operating system. The file ntdll.dll has a description of “NT Layer DLL”. The file ntdll.dll contains NT kernel functions, so it is essential for the normal function of the Windows operating system.
So the above scans should have found corruption if it existed. I was internet connected when I ran them so they functioned proplerly.
Honestly, not trying to be difficult here. I enjoyed your mod last time I played it and wanted to be able to play it again to see how far it's come without having to sacrifice other mods I also enjoy. I do appreciate the work you guys have done on this and I'm sure this time will be just as enjoyable as the last.
@SuperMartijn642 what are your libs doing? any idea what could cuase this weird interaction?
Used the following, administration level command prompt, no errors
sfc /scannow Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /CheckHealth
The file ntdll.dll is a DLL (Dynamic Link Library) file stored in the system folder of Windows operating system. It is usually created automatically during the installation of the Windows operating system. The file ntdll.dll has a description of “NT Layer DLL”. The file ntdll.dll contains NT kernel functions, so it is essential for the normal function of the Windows operating system.
So the above scans should have found corruption if it existed. I was internet connected when I ran them so they functioned proplerly.
Did you also restart your computer after that ?
Entangled 1.3.10 Packed Up 1.0.25 Scarecrow's Territory 1.1.4 Wormhole Portals 1.1.9b
Apart from Packed Up, those mods themselves don't directly interact with the file system. The only thing I can think of is my config library, since of all those mods do use it for config files.
The config library just uses Night Config's CommentedFileConfig under the hood though, it doesn't directly write anything to file.
Apart from that, I don't think my libraries really interact much with the system. My core library is mostly just some default implementations for tile entities, guis, etc. and helper classes.
@trogarus Could you test if the same issue occurs with Future Pack and another mod Durability Tooltip. Durability Tooltip just requires my config library and not the core one. Durability Tooltip itself is also a very simple mod, so if it still crashes, it is just something todo with my config library.
Sure. I'll just put together a pack with Futurepack and Durability tooltip and see what happens. Got some stuff going on, so might take a day or two, but I'll do this and report back.
Also, I did the powershell stuff too that you posted above @mcenderdragon. Still didn't fix the issue. Right now, with the pack, I'm just playing it without the mentioned mods that seemed to help create the conflict.
So, I did two things. I created an instance with nothing but Futurepack and Mod Durability Tooltip. No issues.
Then I added it to the modpack that's been crashing. Here's updated files related to that add.
Current Pid error log https://gist.github.com/trogarus/bfbaed692ca06f542d2efec3525d7a26 Current Debug log https://gist.github.com/trogarus/0428d0906d246fb65e81cc310d4e6db9 FP-Latest log https://gist.github.com/trogarus/067518ce3245e8a09110d73fcf95327f Latest log https://gist.github.com/trogarus/48517f519ad4b02ddfaed9250ea96f6c
And yes @mcenderdragon, I have restarted after attempting to uninstall java, then after re-installing java (which I've done now a couple times trying to deal with this). I also did restarts after running the various administration command prompts and the power shell you mentioned.
Your first two pid crash logs seem to come from the same code path during (what looks like) the FMLCommonSetupEvent. Your latest pid crash log (and latest.log) seems to occur at a different place, something to do with saving dimension data.
From your previous comments I got the impression that it simply crashes everytime during startup of the client.
Is this correct or does it crash at some other point?
Your last crash seems to occur when saving a dimension. The only thing mods like Entangled and Wormhole would contribute to this is block entity data in the form of nbt, which should be no different from something like a regular chest.
So, I did two things. I created an instance with nothing but Futurepack and Mod Durability Tooltip. No issues.
You previously confirmed your pack does startup fine when Future Pack is disabled. Since my mods you mentioned don't have much in common, I was wondering if the issue is actually specific to a combination of my mods and Future Pack. To test this, does your pack also crash when all of my mods you mentioned (including the core and config library) are disabled, but Future Pack is enabled? (Thank you for all the testing you did so far by the way 🙂)
As a last note, I also tried to recreate the issue. I added Future Pack and all of my mods to a 1.18 CurseForge instance, all with the versions you mentioned and the same Forge version, and it starts without a problem. From this and from what I've gathered from the conversation, it seems like it is something specifically with your system. Especially since pid crashes, as far as I know, are usually something caused either by OpenGL, the JVM, or some native dll. (I may be wrong though, this is just when I've encountered pid crashes previously)