Automatically send bug reports when internal errors are encountered

This morning, I submited the following SCR:

http://www.intellij.net/tracker/idea/viewSCR?publicId=10793

What about being able to automatically show a dialog window for sending a
mail to JetBrains, when an internal error is encountered ? Instead of seeing
the infamous "Internal Error" poping up into your face, a dialog box could
be provided with :

- a message field in wich the user would enter some information regarding
the way this internal error happened,
- a stacktrace would be attached to the mail, or sent in the body of the
mail

Moreover, it might be useful to be able to define the mail address of the
sender, and a mail server or SMTP relay.

On the other end, someone at JetBrains would receive those bug-mails, and
would decide wheter to fill an SCR or not.
Because it'd be stupid to automatically submit it as a bug into the tracker,
since several users might submit several times the same bugs !
More clever would even be to parse the stacktrace in order to know whether
it has already been submitted.

Any suggestions regarding this feature ?
I think it might be really handy especially during the EAP process.

Guillaume Laforge


4 comments

Personally, I feel that most of the stack traces have already shown up on
the JetBrains' machines while using the product (that is, known bugs). I say this
because for me, they show up again and again. Such as system as you suggest would
be more useful in production or later EAP stages, for detecting rarely-occurring bugs.
(Even though Mozilla does use it for their beta versions).

Guillaume Laforge wrote:

This morning, I submited the following SCR:

http://www.intellij.net/tracker/idea/viewSCR?publicId=10793

What about being able to automatically show a dialog window for sending a
mail to JetBrains, when an internal error is encountered ? Instead of seeing
the infamous "Internal Error" poping up into your face, a dialog box could
be provided with :

- a message field in wich the user would enter some information regarding
the way this internal error happened,
- a stacktrace would be attached to the mail, or sent in the body of the
mail

Moreover, it might be useful to be able to define the mail address of the
sender, and a mail server or SMTP relay.

On the other end, someone at JetBrains would receive those bug-mails, and
would decide wheter to fill an SCR or not.
Because it'd be stupid to automatically submit it as a bug into the tracker,
since several users might submit several times the same bugs !
More clever would even be to parse the stacktrace in order to know whether
it has already been submitted.

Any suggestions regarding this feature ?
I think it might be really handy especially during the EAP process.

Guillaume Laforge



--

Erb

==============================================================
"Most of you are familiar with the virtues of a programmer.
There are three, of course: laziness, impatience, and hubris."
- Larry Wall
==============================================================

0

Such a system would also be useful for determining if a bug is very
critical or not. If many users experience the same problem the problem
could get a high priority. If only a few users in very special
circumstances or configurations see the error a lower priority could be
assigned to the problem (sort of like Mozilla "topcrash" bugs).

Bas

0

Hello Erb,

"Erb" <dont@evenbother.com> a ?crit dans le message de news:
b5seen$a8d$1@is.intellij.net...

Personally, I feel that most of the stack traces have already shown up on
the JetBrains' machines while using the product (that is, known bugs).


I'm not sure ! If they had encountered these internal errors often, they
would have fixed them already, before building a new EAP release. I'm pretty
sure that 75% of all internal errors don't appear that often. Indeed, I
believe they often miss some critical bugs, such as syntax highlighting of
JSP in the previous build.

I say this
because for me, they show up again and again. Such as system as you

suggest would

be more useful in production or later EAP stages, for detecting

rarely-occurring bugs.

(Even though Mozilla does use it for their beta versions).


In both situations, I think it would be a useful feature.

Guillaume Laforge


0


"Bas Leijdekkers" <basleijdekkers@hotmail.com> a ?crit dans le message de
news: b5sm6a$1rb$1@is.intellij.net...

Such a system would also be useful for determining if a bug is very
critical or not. If many users experience the same problem the problem
could get a high priority. If only a few users in very special
circumstances or configurations see the error a lower priority could be
assigned to the problem (sort of like Mozilla "topcrash" bugs).


Exactly !
They would fetch the mail, they would automatically parse the stacktrace
written in the body of the mail (delimited by some strings, or with some
regular expressions), they would recognize it and compare it with a
bug/stacktrace database. Then, they could count the number of times this
internal error appears. It should get a high priority if it is often
encountered.
It really sounds good, and could automate the process of quickly fixing
those often encountered bugs.

Guillaume Laforge


0

Please sign in to leave a comment.