<therube>	hi. often times (not always) when i have a crash, the crash reports don't return any information back to me.
	<therube>	they'll go into a "Fetching this archived report will take 30 seconds to 5 minutes" loop, only to eventually return "Oh noes" (or something like that).
	<therube>	how to i get to see my crash reports?
	<rhelmer>	therube: do you mean the mozilla-hosted crash-stats, or your own socorro install?
	<therube>	rhelmer: mozilla (seamonkey)
	<rhelmer>	therube: that could mean that the crashes you are trying to pull up can't be processed.. can you give me an example URL to crash-stats?
	<therube>	like: http://crash-stats.mozilla.com/report/pending/4f7c5277-c1b8-4022-aa9f-1e9902110127
	<rhelmer>	therube: or just the crash ID
	<firebot>	therube: http://crash-stats.mozilla.com/report/index/4f7c5277-c1b8-4022-aa9f-1e9902110127
	<rhelmer>	therube: yeah so I get this message, I think we don't always show it consistently but this is the problem - http://rhelmer.pastebin.mozilla.org/996919
	<rhelmer>	therube: there's a bug on this, the UI should be better.. basically what happened is breakpad minidump_stackwalk can't understand that crash, so we aren't able to process it
	<rhelmer>	it can't figure out which thread actually crashed :/
	<deinspanjer>	150 connections now
	<rhelmer>	mpt-collectors are pushing a little over 10MB/s ... woo
	<therube>	rhelmer: ah, gotcha. so nothing to be returned, so it returns nothing.
	<therube>	ok thanks.
	<rhelmer>	therube: yeah, I think it's exactly what we've been discussing in bug 572174
	<firebot>	Bug https://bugzilla.mozilla.org/show_bug.cgi?id=572174 cri, --, 1.7.7, rhelmer, NEW, Every Camino 2.0.3 "null signature" crash since 11 Jun is missing the actual report
	<rhelmer>	therube: really the UI needs to be more clear, and just show you what it can. do you have access to raw crash dumps?
	<rhelmer>	therube: if so, you can pull that and look at it yourself, or at least get the info the user submitted at crash time
	<therube>	rhelmer: yes. i did take a quick look & saw some textual data, so figured i might be able to do something with it.
	<rhelmer>	therube: yeah you can get the original form submission data as json with e.g. https://crash-stats.mozilla.com/rawdumps/4f7c5277-c1b8-4022-aa9f-1e9902110127.json
	<firebot>	rhelmer: http://crash-stats.mozilla.com/report/index/4f7c5277-c1b8-4022-aa9f-1e9902110127
	<rhelmer>	and the dump with replacing .json with .dump, although that's probably not useful if stackwalk can't grok it
	<rhelmer>	the user might have typed in some useful info though
	<rhelmer>	therube: anyway I think we'll either break out into a separate bug, or morph that bug into "make the UI show something more useful than the oh noes screen when processing fails" :)
	<rhelmer>	hope that helps
	<therube>	rhelmer: the "user" is me :-). in order to use http://crash-... needs a login. yes that helps, thanks.
	<rhelmer>	therube: ah yeah that's what I was wondering when I asked if you had access to raw data
	<therube>	oh.
	<rhelmer>	therube: thought you meant "your crash", like you put the code there that crashed :P
	<therube>	oh no. definitely not that.