MCL-646"Report to Mojang" Button creates blank report without crash report
Not a bug, but a feature request. (Yes, I know...)
In case of a crash the crash report is shown nicely in the launcher, but the Button "Report to Mojang" doesn't attach the crash report automagically. Since most users fail to attach the crash report or even fill out the optional fields ("Description") resulting in a flood of incomplete tickets here:
https://mojang.atlassian.net/issues/?jql=resolution%20%3D%20Incomplete%20AND%20text%20~%20%22without%20crash%20report%22%20ORDER%20BY%20key%20DESC
A compromise would be instead of attaching the crash report to embed it in the description envelopped by {code} tags.
Created Issue:
"Report to Mojang" Button creates blank report without crash report
Not a bug, but a feature request. (Yes, I know...)
In case of a crash the crash report is shown nicely in the launcher, but the Button "Report to Mojang" doesn't attach the crash report automagically. Since most users fail to attach the crash report or even fill out the optional fields ("Description") resulting in a flood of incomplete tickets here:
https://mojang.atlassian.net/issues/?jql=resolution%20%3D%20Incomplete%20AND%20text%20~%20%22without%20crash%20report%22%20ORDER%20BY%20key%20DESCA compromise would be instead of attaching the crash report to embed it in the description envelopped by {code} tags.
It's too large to include automagically. We could put it on pastebin or something, but then that opens up another can of worms and isn't very nice to pastebin.
Shortened report:
First few lines of the stack trace
and a part of the system spec
Minecraft Version: 1.6.1 Operating System: Windows 7 (amd64) version 6.1 Java Version: 1.7.0_25, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 795595136 bytes (758 MB) / 1029046272 bytes (981 MB) up to 1029046272 bytes (981 MB) JVM Flags: 2 total; -Xmx1G -Xms1G Launched Version: 1.6.1 LWJGL: 2.9.0 OpenGL: AMD Radeon HD 6700 Series GL version 4.2.12217 Compatibility Profile Context 12.104.0.0, ATI Technologies Inc. Is Modded: Probably not. Jar signature remains and client brand is untouched. Type: Client (map_client.txt) Resource Pack: Misa500-13w23b.zipShould be enough to identify the standard errors so that the users won't be annyoed by an "Incomplete" resolution (well, "Duplicate" instead...)
Then spam golem isn't going to be able to work his magic, and the user isn't going to attach the full report because it looks like it's already there, and we (devs) won't get to see the info we tried hard to add for debugging.
https://mojang.atlassian.net/secure/Dashboard.jspa?selectPageId=13300
24 % incomplete reports (no crash report provided). A solution is required.
Added text to say "please copy paste the report" but we can't do anything more until we turn Spam Golem into a mojang service. The idea will be to make reports sent to that service and then from there it will either make a new issue or append it to an existing one.
I don't think we really rely that heavily on Spam Golem, so that's not really an issue. The only parts of the crash report that are really useful are:
(Which can all be reported in what Kumasasa suggests)
The only way I can see the file going over 10 MB is if it is one of those infinitely repeating stacktraces. Even if Mojang wants more info and won't get it, a start is better than nothing.
But with this approach, none of this will be an issue at all. There won't be dupe issues because they'll get told to post a comment on the main issue (which will automatically contain a link to the crash report) or they'll get told to make a new issue which again will automatically have a link to the crash report. Win win!
Okay. Resolving as fixed.
Go Hopper, go !