Reply to thread

Message

Hi Aaron,
Unfortunately it is next to impossible to have crash/hang debugging info submissions unless they are generated automatically and at the moment a crash occurs. You can't ask end users to understand how to generate debugging dumps sometime after the crash happens. So usually when MP crashes, debugging dumps and needed info can be generated and the option to send them, or not.

I do get the feeling from yours and other "official" replies above that a conclusion has been jumped to about what exactly such a crash submission is, but at the same time the comments show that there is a lack of understanding about what it is, what it involves or how it works in production environment. It makes more sense to use such a system when only 5% off developers are active, not less. It saves time and improves stability, not less. There are many projects out there of all shapes and sizes to use as an examples, I just chose some people were sure to have heard of - you do not need to be Mozilla. One man bands are more suited to this than Mozilla is.

However its probably best I leave it there. I am not trying to ram this simple idea down your throats or anything . I have only wanted to open up the idea for consideration. Informed consideration that is, not "oh thats just emailing the logs and system info automatically, we considered that, no thanks". Thats just incorrect and mis-informed.
I have been on enough developer teams by now to know how it works - who know's maybe we worked together at some point in Aussie, going by the sound of your work summary .

Have a good one,
Keith.

<blockquote data-quote="krntea" data-source="post: 161504" data-attributes="member: 28550">Hi Aaron,&nbsp;&nbsp; Unfortunately it is next to impossible to have crash/hang debugging info submissions unless they are generated automatically and at the moment a crash occurs. You can't ask end users to understand how to generate debugging dumps sometime after the crash happens. So usually when MP crashes, debugging dumps and needed info can be generated and the option to send them, or not.&nbsp; I do get the feeling from yours and other &quot;official&quot; replies above that a conclusion has been jumped to about what exactly such a crash submission is, but at the same time the comments show that there is a lack of understanding about what it is, what it involves or how it works in production environment. It makes more sense to use such a system when only 5% off developers are active, not less.&nbsp; It saves time and improves stability, not less.&nbsp; There are many projects out there of all shapes and sizes to use as an examples, I just chose some people were sure to have heard of - you do not need to be Mozilla. One man bands are more suited to this than Mozilla is.However its probably best I leave it there. I am not trying to ram this simple idea down your throats or anything <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />. I have only wanted to open up the idea for consideration. Informed consideration that is, not &quot;oh thats just emailing the logs and system info automatically, we considered that, no thanks&quot;.&nbsp; Thats just incorrect and mis-informed.I have been on enough developer teams by now to know how it works - who know's maybe we worked together at some point in Aussie, going by the sound of your work summary <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />.Have a good one,Keith.</blockquote>

[QUOTE="krntea, post: 161504, member: 28550"] Hi Aaron, Unfortunately it is next to impossible to have crash/hang debugging info submissions unless they are generated automatically and at the moment a crash occurs. You can't ask end users to understand how to generate debugging dumps sometime after the crash happens. So usually when MP crashes, debugging dumps and needed info can be generated and the option to send them, or not. I do get the feeling from yours and other "official" replies above that a conclusion has been jumped to about what exactly such a crash submission is, but at the same time the comments show that there is a lack of understanding about what it is, what it involves or how it works in production environment. It makes [B]more[/B] sense to use such a system when only 5% off developers are active, not less. It saves time and improves stability, not less. There are many projects out there of all shapes and sizes to use as an examples, I just chose some people were sure to have heard of - you do not need to be Mozilla. One man bands are more suited to this than Mozilla is. However its probably best I leave it there. I am not trying to ram this simple idea down your throats or anything :-). I have only wanted to open up the idea for consideration. Informed consideration that is, not "oh thats just emailing the logs and system info automatically, we considered that, no thanks". Thats just incorrect and mis-informed. I have been on enough developer teams by now to know how it works - who know's maybe we worked together at some point in Aussie, going by the sound of your work summary :-). Have a good one, Keith. [/QUOTE]