896438 - Intermittent browser_pluginnotification.js | Test 12a, Should have a click-to-play notification | uncaught exception - TypeError: popupNotification is null at browser_pluginnotification.js:263

Status: RESOLVED DUPLICATE of bug 896965

(Core Graveyard :: Plug-ins, defect, P3)

Description

[Carsten Book [:Tomcat]]

https://tbpl.mozilla.org/php/getParsedLog.php?id=25544836&tree=Mozilla-Central

Windows XP 32-bit mozilla-central pgo test mochitest-browser-chrome on 2013-07-21 06:42:20 PDT for push eaabf1f668ff

slave: t-xp32-ix-048

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/browser_pluginnotification.js | Test 12a, Should have a click-to-play notification

also followed by 

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/browser_pluginnotification.js | uncaught exception - TypeError: popupNotification is null at chrome://mochitests/content/browser/browser/base/content/test/browser_pluginnotification.js:263
06:45:31     INFO -  Stack trace:
06:45:31     INFO -      JS frame :: chrome://mochikit/content/tests/SimpleTest/SimpleTest.js :: simpletestOnerror :: line 1136

Comment 1

[Ed Morley [:emorley]]

(Adding the exception to the summary, in case it happens elsewhere)

Comment 2

[Georg Fritzsche [:gfritzsche]]

This is right after loading plugin_clickToPlayAllow.html, which does nothing special - no dynamically loaded plugins etc:
http://hg.mozilla.org/mozilla-central/annotate/308e3cf5ba75/browser/base/content/test/browser_pluginnotification.js#l251

The next test function is already run delayed here:
http://hg.mozilla.org/mozilla-central/annotate/308e3cf5ba75/browser/base/content/test/browser_pluginnotification.js#l89

... so i'm not sure why this would happen here. We should have gotten a "PluginBindingAttached" event at this point with "PluginClickToPlay", which should have resulted in the notification being shown.

Comment 3

[Ed Morley [:emorley]]

15:37:20 - gfritzsche: RyanVM, edmorley: those "notification missing" failures there can really go together as long as there are no other weird errors mixed in... they all look to be the same issue

Duping to the bug with the most info