gtg team mailing list archive

[Bryce Harrington <bryce@xxxxxxxxxxxxxxxxxxx>]

Agreed; crashing is bad enough, but when these multi-crash-notices pop
up it makes things appear worse than they really are.

(It might be nice to have a command-line way to disable the crash
handler entirely, for the (rare) cases when you need to run the app
through pydb.)

** Changed in: gtg
       Status: New => Confirmed

-- 
Crash handler should never be displayed more than once
https://bugs.launchpad.net/bugs/594975
You received this bug notification because you are a member of Gtg
contributors, which is subscribed to Getting Things GNOME!.

Status in Getting Things GNOME!: Confirmed

Bug description:
The crash handler is displayed for every crash. It means that if a non-critical crash happens in a loop, you will get plenty of crash handlers.

It makes GTG very hard to debug and provides a very bad experience for non-critical crashes.

The handler should never be called more than once per session (at worst, we will simply miss some crashes)