Search results

Zero crashes of this type on 1.9.4 this week. Seems promising.

Previously I was on 1.12. The crashes seem less frequent, but that could also just be because I'm playing less frequently. :-)

It might just be my imagination, but this bug seems less frequent. To help with the bug reports, I've been asked to do the following: + Play on version 1.9 + Get the output of /whereami prior to a crash (this means record it for every game since the crashes are random.) + Submit a crash report...

Current status: Your bug report has been denied. Message from the staff member : Hello, once again this is another situation that there isn't a specific reason for this error and we do not know what the issue is. The error means that something went wrong when decoding something, this is most...

I tried 1.11.2 (vanilla, no mods) and get the same crashes with a different stack trace: java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.Integer at zp.di(SourceFile:214) at zp.A_(SourceFile:148) at sn.aw(SourceFile:1628) at sw.aw(SourceFile:1940)...

Current status: "Your bug report is currently waiting to be viewed"

I've submitted a bug report for this common issue-- while playing Tower Defence the game will abort with the message: Internal Exception: io.netty.handler.codec.DecoderException: Unknown serializer type 14 I didn't see any other postings about this bug on the forums. It's probably the second...

I'm playing on a completely unmodded copy of Minecraft and frequently get "The game crashed whilst ticking entity" bug, so it's not mod-related. Sample stack trace: java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.Integer at acs.dm(SourceFile:214) at...

I finally got /registerreports working and reported this same bug with multiple crash reports. Here's part of one: https://pastebin.com/66RqMXrF They all have the same entity being ticked (creeper) Interestingly the source file name changed since May, but the source line has not. -- Head --...

Use /registerreports from a lobby to get a secret URL to the bug reporting system. (It's currently working-- it breaks a lot so if you get the dreaded "Error code 2" just try again tomorrow and repeat until it works.) I've reported the same bug with MANY crash reports so hopefully they'll get...