[dev_north_east]

I feel you.

> I can backlog it as a bug, but it's not going to be easily searchable.

In my experience, I've marked it as a bug, comment with the stack trace and mark as U. Then when it arises again, hopefully someone searches for a part of the stack and comes lucky or more often than not, I (or others) will hear of the crash and relay the bug info. Bug is updated with any new info and live continues until it crashes again... Not perfect by any means. I'd love to hear how others deal with this

[quickthrower2]

I’ve also: Added more logging code for future cases, and or try to reason about how it could have occurred. Try to make it impossible if you can, but sometimes that requires too big of a rearchitecture to be worth it.