[MC-5289] MC 1.4.6 Crashes While at Top of Beacon Beam Created: 23/Dec/12 Updated: 10/Feb/13 Resolved: 23/Dec/12 |
|
| Status: | Resolved |
| Project: | Minecraft: Java Edition |
| Component/s: | None |
| Affects Version/s: | Minecraft 1.4.6 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Avantir_Yihn | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Mac OS X 10.7.5 Lion, Java 1.6 |
||
| Issue Links: |
|
||||||||
| Confirmation Status: | Unconfirmed | ||||||||
| Game Mode: | Creative | ||||||||
| Description |
|
I was flying around y:300 looking at the top of a Beacon Beam and the game randomly froze for a few seconds then crashed when I was moving around/in the beam. It was NOT an out of memory error. ---- Minecraft Crash Report ---- Time: 12/23/12 11:50 AM java.lang.IllegalStateException: Entity is already tracked! A detailed walkthrough of the error, its code path and all known details is as follows: – Head – – Affected level – – System Details – |
| Comments |
| Comment by WolfieMario [ 24/Dec/12 ] |
|
That isn't necessarily the case. Many crashes like these are error checking in Minecraft - in this case an IllegalStateException. There may be a level loading issue causing the illegal state in the End, while an entity rendering issue may cause the issue here. When the cause of one bug is different than another, it's highly unlikely for both to be fixed with a single change. The reason the stack trace is the same is because the system has entered an illegal state in both situations - the underlying cause is not always present in a stacktrace. |
| Comment by Tails [ 24/Dec/12 ] |
|
Possibly the crash has nothing to do with The End, but the stack trace of the crash is the same. |
| Comment by WolfieMario [ 24/Dec/12 ] |
|
How is this a duplicate of that? The End and beacons are entirely unrelated. "java.lang.IllegalStateException: Entity is already tracked!" doesn't automatically mean it has the same cause - at that rate, you may as well consider all NullPointerExceptions the same bug. |
| Comment by Tails [ 23/Dec/12 ] |
|
Duplicate of |