The notification popup received when UI freezes are detected display a stacktrace which always seem to refer to the automatic error reporting code itself, and not to where the actual problem lies. See attached screenshot.
If it is not possible to show the stack trace of where the UI freeze occurs, it is better not to show a stack trace at all. Even as a fairly experienced Eclipse plugin developer, I was thrown off by this, and I suspect that other users will be confused as well.
IMHO, if these popups are intended for "normal" Eclipse users (as opposed to plugin developers), referring to plugin ids and stack traces in a notification such as this probably not a good idea.
I get your point. A simple improvement would be to just show the simple class name. Then it would not be *that* misleading. A special treatment for UI freezes, however, seems a bit like an overkill IMHO. But maybe a the discussion in bugzilla will change my mind...