that when a blender crashes to open a crash report window similar to that of a VLC media player:
75%
Development Status:
Open
Upvote12Downvote4
i
ivek.burek
16 Aug 2021
4 Comments
W
WickedInsignia
Immediately presenting a log of the crash conditions which could be delivered to the team in a bug report would be very useful. It would certainly be faster than digging around for debug logs.
An alternative to automatically sending the data (who would read it and implement fixes? Where would this repository even be stored?) would be to save the log file to desktop, and have a new bug report window open in the browser ready to be filled out with the log attached. This would at least encourage users to take the time to make a bug report, since most of the work is already done for them.
2
b
bestelix
In my experience crahses are mostly generated by addons so the report should go to their developpers. This seems complicated to sort and I wouldnt put this on blender's team. For the rest, especially the ones in alpha, I think the system works well as it is now with user's mediation as blender is a community product.
1
K
Kdaf
Who will sort the crash reports to validate them one by one ? Checking duplicates, etc ...
I think it is time consuming.
k
ktdfly
I think, automatic reports rarely will be watched manually. But
statistics
on crashes is a rather meaningful thing. Statistics can include which addons were activated, versions, system properties and so on. This stats can easily reveal, e.g. that Blender on one OS crashes more often then on another, or that some addon is responsible for 5% crashes. Addons and Blender developers will find different slices of the same data more applicable for each of their purposes.
4 Comments
Immediately presenting a log of the crash conditions which could be delivered to the team in a bug report would be very useful. It would certainly be faster than digging around for debug logs.
An alternative to automatically sending the data (who would read it and implement fixes? Where would this repository even be stored?) would be to save the log file to desktop, and have a new bug report window open in the browser ready to be filled out with the log attached. This would at least encourage users to take the time to make a bug report, since most of the work is already done for them.
In my experience crahses are mostly generated by addons so the report should go to their developpers. This seems complicated to sort and I wouldnt put this on blender's team. For the rest, especially the ones in alpha, I think the system works well as it is now with user's mediation as blender is a community product.
Who will sort the crash reports to validate them one by one ? Checking duplicates, etc ...
I think it is time consuming.
I think, automatic reports rarely will be watched manually. But statistics on crashes is a rather meaningful thing. Statistics can include which addons were activated, versions, system properties and so on. This stats can easily reveal, e.g. that Blender on one OS crashes more often then on another, or that some addon is responsible for 5% crashes. Addons and Blender developers will find different slices of the same data more applicable for each of their purposes.