Closed Bug 635057 Opened 13 years ago Closed 9 years ago

"aTab is null" error when sending Plugin crash report via the notification bar

Categories

(Firefox :: Tabbed Browser, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: whimboo, Unassigned)

Details

(Keywords: regression, Whiteboard: [4b12])

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b12pre) Gecko/20110217 Firefox/4.0b12pre

If your Flash plugin crashes i.e. on YouTube, you will get a notification bar. Clicking on send report, will not open a new tab, but produces the following error:

Error: aTab is null
Source File: chrome://browser/content/tabbrowser.xml
Line: 1931

Reloading the page directly afterward shows another error:

Error: uncaught exception: [Exception... "Node was not found"  code: "8" nsresult: "0x80530008 (NS_ERROR_DOM_NOT_FOUND_ERR)"  location: "chrome://global/content/bindings/notification.xml Line: 151"]

As far as I can see the crash report gets submitted, so it's not a critical issue.
Whiteboard: [4b12]
Safe to say this is WFM these days? :)
Flags: needinfo?(hskupin)
I have no easy way to get this tested. So closing as incomplete.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(hskupin)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.