Opened 10 years ago
Closed 10 years ago
#3355 closed enhancement (worksforme)
OMEdit automated crash report
| Reported by: | Francesco Casella | Owned by: | Adeel Asghar |
|---|---|---|---|
| Priority: | high | Milestone: | 1.9.3 |
| Component: | OMEdit | Version: | trunk |
| Keywords: | Cc: | marco.lovera@… |
Description
A colleague of mine reports that he basically cannot use OMEdit to do any serious work because the GUI crashes too often to be usable.
Unfortunately, this kind of problem is not easily reproduced due to its erratic nature. On the other hand, it is absolutely essential to improve the robustness of the tool to encourage its usage for serious projects.
I would recommend that we include in OMEdit some facilities for post-mortem debugging and automatic reporting, as other programs do, e.g. Mozilla Thunderbird and Firefox. I guess this could help a lot resolving issues that would otherwise remain unreported forever.
Change History (3)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Maybe the crash is associated with the "too many heap sections"?
There was already some discussion about it on ticket #3318.
comment:3 by , 10 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
OK, thanks, maybe he hasn't tried him out for a while. I have recommended him to try once more.
We already have this feature. When the GUI crashes the user is presented with a
Crash Reportdialog where he can specify the problem. The dialog also allows to specify which log files user wants to send along with the crash report.