Apparently, we actually know this. According to billm, the "hang evidence" that is sent up from the content process contains enough data for us to map the hang to a particular <xul:browser>. So the notification bar we display could be more specific about the tab causing the hang. For example, it could display the URI. Or it could have a button or link to select the hanging tab if it's in the background (or different text if the hanging tab is currently selected).
7 months ago