search

Hamster-Systems / Hbm-s-Nuclear-Tech-GIT

GNU General Public License v3.0
4 stars 2 forks source link

Crash while exploring Twilight Forest on server #27

Closed aking4125 closed 7 months ago

aking4125 commented 7 months ago

Hello,

Upon exploring the twilight forest, clients are crashing with the following report:

crash-2023-11-12_16.39.58-client.txt.zip

latest.log.gz

In the log, HBM is referenced multiple times. The original crash report doesn't seem to give too much information.

Any ideas?

itech2018 commented 7 months ago

I noticed in your reply you said some clients. Is this just happening to a select few people

aking4125 commented 7 months ago

Yes. I am so far unaffected. At least in those same chunks. Since I'm about 2k blocks away from them.

I'm testing the world save on a SP world to see what is up in that area.

itech2018 commented 7 months ago

Yeah let me know what happens with a test in single player as the log file and crash log at a quick look dont seem very helpfull

aking4125 commented 7 months ago

Yeah. CensoredASM is pointing directly to HBM and those repeated crashes found in the .log file. HBM is referenced the most for some reason. Then the references stop, points to bewitchment, then points to nothing else. So I'm a tad confused as to what is happening.

Since HBM is referenced the most, that's why I posted this here for a tiny bit of insight knowing full well it doesn't contain any useful information.

itech2018 commented 7 months ago

Yeah HBM Can often get the blame for it due to errors from things like textures of removed blocks that have been removed but the physical block has been left behind for backwords compatibility

aking4125 commented 7 months ago

Referenced this issue to Gregtech since the single-player crash now points directly to Gregtech. Further complicating the issue I guess.

Also its not just some clients, confirmed to be everybody.

aking4125 commented 7 months ago

This issue is unrelated to HBM as it was just a packet-sending problem. Gregtech seems to be the cause. May reopen if anything HBM-related shows up. See the mentioned issue for details.