home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
Bug/Crash submission system
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="tomtom21000" data-source="post: 161541" data-attributes="member: 10287"><p>Hi Keith, I really appreciate your idea. I can´t really judge on the pro´s and con´s as I am no developer. But I´d like to raise some points:</p><p></p><p># From my experience and from reading the forums on a daily basis for a long time, crashes are rare in MP. They may occure more frequently with the tve3 which i don´t use so far. I had like 5 crashes the past two years with MP. Note that I update svn very often, that I have installed about 15 plugins, test new ones often and change skins frequently. I allways install over the last one and do all this on my productive htpc environment. I filed a lot of bug reports over the time, but 95% are about bugs in functionality, navigation etc.</p><p></p><p>If this is not only my perception, but true, the value of a crash report system comes down to a question of efficiancy.</p><p></p><p># I never sent a crash report to MS, and I didn´t install the quality assurance tool from firefox. call it paranoia. Maybe my personal view.</p><p></p><p># The htpc scene is still a domain of computer geeks. I estimate 90 % have something having to do with computers as a profession. So you have a good chance to get some meaningful bugreports on a forum system (I bet infinityloop doesn´t agree <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> ). I think having a report "do Step1, Step2, Step3 -> bug" helps a lot like aaron said. I could imagine that doing that was related or even necessary to produce the bug is important to know. Could you know that from an auto bug report?</p><p></p><p># Could you tell from the reports, which belong to the same bug? Would there be an easy way to detect that they all use a certain filter or hardware? Not easy on forum reports either. Could be a plus if possible.</p><p></p><p>Not speaking for or against it, I am in no position to do so. But if this suggested system was only helpful in a minority of the bug scenarios (crashes), it is really a question of the cost/gain-ratio.</p><p></p><p>tomtom</p></blockquote><p></p>
[QUOTE="tomtom21000, post: 161541, member: 10287"] Hi Keith, I really appreciate your idea. I can´t really judge on the pro´s and con´s as I am no developer. But I´d like to raise some points: # From my experience and from reading the forums on a daily basis for a long time, crashes are rare in MP. They may occure more frequently with the tve3 which i don´t use so far. I had like 5 crashes the past two years with MP. Note that I update svn very often, that I have installed about 15 plugins, test new ones often and change skins frequently. I allways install over the last one and do all this on my productive htpc environment. I filed a lot of bug reports over the time, but 95% are about bugs in functionality, navigation etc. If this is not only my perception, but true, the value of a crash report system comes down to a question of efficiancy. # I never sent a crash report to MS, and I didn´t install the quality assurance tool from firefox. call it paranoia. Maybe my personal view. # The htpc scene is still a domain of computer geeks. I estimate 90 % have something having to do with computers as a profession. So you have a good chance to get some meaningful bugreports on a forum system (I bet infinityloop doesn´t agree ;) ). I think having a report "do Step1, Step2, Step3 -> bug" helps a lot like aaron said. I could imagine that doing that was related or even necessary to produce the bug is important to know. Could you know that from an auto bug report? # Could you tell from the reports, which belong to the same bug? Would there be an easy way to detect that they all use a certain filter or hardware? Not easy on forum reports either. Could be a plus if possible. Not speaking for or against it, I am in no position to do so. But if this suggested system was only helpful in a minority of the bug scenarios (crashes), it is really a question of the cost/gain-ratio. tomtom [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Bug/Crash submission system
Contact us
RSS
Top
Bottom