Upon joining my creative world (which has quite a bit of redstone) the game immediately crashed due to what is definitely a StackOverflowException. In the crash report, it simply repeats this over and over:
at yc.m(SourceFile:445)
at yc.h(SourceFile:429)
at alv.a(SourceFile:185)
at zz.a(SourceFile:367)
at zz.a(SourceFile:331)
at yc.b(SourceFile:315)
at yc.e(SourceFile:362)
at alv.a(SourceFile:225)
at yc.m(SourceFile:442)
at yc.h(SourceFile:429)
at alv.a(SourceFile:185)
at zz.a(SourceFile:367)
at zz.a(SourceFile:331)
at yc.b(SourceFile:315)
at yc.e(SourceFile:362)
at alv.a(SourceFile:225)
Above that it gives some details about updating redstone:
Details:
Source block type: ID #55 (tile.redstoneDust // alv)
Block type: ID #55 (tile.redstoneDust // alv)
Block data value: 0 / 0x0 / 0b0000
Block location: World: (217,92,1073), Chunk: (at 9,5,1 in 13,67; contains blocks 208,0,1072 to 223,255,1087), Region: (0,2; contains chunks 0,64 to 31,95, blocks 0,0,1024 to 511,255,1535)
It has a very long list of very similar details under the stack trace explained above. My assumption is, with my being fairly fluent in Java, there was an infinite loop in updating some redstone where one redstone block updated something which updated the redstone which updated that something again, causing an infinite loop, leading to the StackOverflowException.
Attachments
Comments 4
Please do not mark issues as private, unless your bug report is a security issue containing information that may compromise your server/client.
No, it does not. And sorry about marking it as private; I simply wanted to prevent people from commenting on how they could not reproduce it since it's not actually 13w07a. Also, just for clarification, the obvious issue was the fact that I had some of the new blocks (new as of 1.4.7) and they were causing issues.
I just realized I was not in 13w07a.... Very embarrassing. My bad, disregard this.