Option to send an error report when Tribler is stuck at shutdown

[xoriole]

Sometimes Tribler is stuck at shutdown which is not easy to reproduce. Currently, after a while, we show the users a button to force shutdown. In such a case, if we provide an option for the user to send us an error report, it will help us better understand the reason why Tribler was stuck.

[synctext]

Very good idea. This 'stuck' (== long wait of 10+ minutes) at shutdown is trivial to reproduce, just leave running for few days. Then shutdown takes long. Perhaps the checkpoints to 30 swarms take a while to commit to disk. Libtorrent IO still seems to act out on Tribler. This would be great way to diagnose the 10-15 minute shutdown duration on a 6-years old Mac by User 0.

[drew2a]

@xoriole

In such a case, if we provide an option for the user to send us an error report.

How do you see the formation of the error report in this case? I'm asking because it is not obvious, and I want to know your view. If Tribler is stuck at shutdown, there would probably be no errors, just slow operations. Our FeedbackDialog method of sending errors assumes that you have an actual exception.

[qstokkink]

The extended shutdown status reported by the new Tribler core code resolves this issue.