Maxwell Mcphearson Paradise
Assigned
Reported
Comments
The real thing is that I never experience it. Maybe it's a distinct computer version or java or something?
Theoretically, we need to try and isolate where the glitch/bug occurs, and what Enviornment it happens on most often.
I believe that would speed up the bug fixing.
(NOTE: This also occurs on Console Edition MineCraft)
Yeah, it's chance of happening has dropped significantly. It still is annoying, even though it doesn't effect me directly, I see other players complaining about it. Trust me, it is quite annoying for me. I make my own skins, and the bug really set me back.
It's okay. I didn't know it was the same for everything. But hey, lack of RAM does cause game crashes, still, right? If so, it is most likely the cause. It is common, and lack of RAM shuts off some of my favorite games (Not Minecraft, i treat it with care, and music apps, like a Max)
In fact, we need to update the Launcher to display what exactly caused the crash... would be mighty good if i say from a young, overly intelligent gamer's perspective.
(I wish i was a mod, but hey, i'm not even old enough to have a driver's license, so why should i care? XD)
Nevermind
What most likely happened (Like most generic "WHAT HAPPENED?!" crashes) Your computer probably didn't have enough RAM to run Minecraft anymore, forcing a shutdown/crash of Minecraft. In turn, the "[5:26:05 p.m. INFO] Ignoring visibility rule and showing launcher due to a game crash" part is perfect proof that this is most likely the case. Minecraft only obeys this rule when it knows what's going on (Typically).
Solution/Resolution:
1: Play Minecraft without running many programs (Reduces RAM needed)
2: Increase RAM cap (Allows for more memory to be used to keep games like it from crashing)
3: Try not to push Minecraft's limits. The thing is kind of sensitive.
With regards to help a fellow gamer, MineSteinMax (Maxwell)
(Edit: It was kind of hard to understand. User proper grammar and use spell check.)
Okay, Sure. Updating it to fit that, as I just saw players experiencing it.
(EDIT: I think it just might be a error in realizing that the website Minecraft.net has sent a new skin, and it ends up defaulting. Might not be the cause, but I think I'm close to the actual cause, I might see if I can analyze the file(s), even though I'm one heck of a rookie at this still.)
This issue also occurs in Console Title Updates 14 and above (Technically update 1.4.7) So try and get some data from consoles as well.
I think a viable solution is to [Partially] use hit boxes to detect ground and objects around. I might actually open up with this topic, and it might have to do with the skin bug occurring that i have reported. Then again, hit boxes are not always reliable. but try it out in a test version, will you? It might just work.
Okay, Everyone, it is now all clear to me.
Get an actual log of what goes on in the scripting before, during, and after the exception has occurred. After that, i can try and use my knowledge to give suggestions.
Major Edit:
It seems that the possibility becomes quite high after it is achieved once. It might be that the game attempts to switch files and ram, and shuffles two files needed in two places back, then "remembers" the pattern for "convenience" without even knowing it is causing the error. Or.. it could be the work of the villager overlord serving us... wanting revenge... Okay, joking. But really, see if my theory is valid.
I know i'm not some genius, but have you tried using color code detection to make sure un-dyed leather Armour from using up water?
EX. Item | Use on cauldron enabled
Leather armor | Allowed
(Color#EXAMPLE) |
Leather armor | Action disabled, no ID specifying to color
(Undyed) |
@Andrew, Hmm. I thought there would be some sort of clue. did you force a crash with
F3 + C for 10s?
@MJ Cortez, This Exception is quite difficult to solve. the crash coding isn't showing anything. I used to experience this when my internet was really hiccuping, or that...
Aha! It might be that two IP's afflict one another due to their similarity.
Ehh. Maybe not. 😛
Well, analyzing the file you have sent ever so kindly...
You need to try and reproduce this, and find how common it is at certain times.
(NOTE: I used to get it, but i thought that "TimeOut" meant either
1. I went AFK too long.
2. I lagged too long.
3. Servers are just jerks.
After i found out it was a bug, I wasn't too shocked. Most certainly, i don't get it now. The only time I get the error is when too many people are lagging, or when there was too much modification to the server, causing too much lag. I wish I could solve it, but it seems there is no unusual behavior with the report.
@CraftyMiner, That's interesting. VERY interesting.
Okay, guys, i will try and cause the Timeout Exception, but i need to know how to trigger it. I know it sounds simple, but i don't remember how to simply cause it anymore, since in 1.7.9, it seems that I don't get it.
(NOTE: Confirm for 1.7.9, as I need PROOF that it still occurs. (at least in any version that is or past 1.7.9, pre-release or not)