[Crash Reporter] Crash in TourHandler processing routine
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Randomly
Status
active
Regression
No
Workaround
No
Project
No steps. Crash report is attached.
Attachment | Size |
---|---|
664deb09a0c14d0fa6b66c11e42af533-symbolicated.txt | 47.68 KB |
Comments
And one more crash report
And more. Looks like a lot of similar crash logs have the same root problem: TourHandler
Is that really the case, though? Isn't that just an event filter that happens to be on the call stack, and the stuff on the top of the stack is more relevant? That is, aren't all events processed through those filters?
relates to #289587: [EPIC] Most frequent crash reporter events
In reply to Is that really the case,… by Marc Sabatella
Very good question! Investigation is needed anyway.