Open Bug 800957 Opened 13 years ago Updated 3 years ago

xpcIJSWeakReference.get throws an exception intermittently

Categories

(Core :: XPConnect, defect)

15 Branch
x86_64
Windows 7
defect

Tracking

()

REOPENED

People

(Reporter: barancev, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4 Steps to reproduce: Inspired by Selenium issue 4309 (http://code.google.com/p/selenium/issues/detail?id=4309) Run the following Selenium script: WebDriver driver = new FirefoxDriver(); driver.get("http://cheapflights.co.uk"); driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS); for (int i = 0; i < 20; i++) { driver.findElement(By.cssSelector("div.home-link-groups a")).click(); driver.navigate().back(); } driver.quit(); Actual results: Intermittently it fails because browser throws an exception: Timestamp: 12.10.2012 20:02:10 Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [xpcIJSWeakReference.get]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///C:/Users/alexei/AppData/Local/Temp/anonymous8072089874289580448webdriver-profile/extensions/fxdriver@googlecode.com/components/session.js :: <TOP_LEVEL> :: line 1453" data: no] Источник: file:///C:/Users/alexei/AppData/Local/Temp/anonymous8072089874289580448webdriver-profile/extensions/fxdriver@googlecode.com/components/session.js Строка: 1453 Expected results: According to specification (http://dxr.mozilla.org/mozilla-central/js/xpconnect/idl/xpcIJSWeakReference.idl.html), xpcIJSWeakReference.get should not throw exceptions, it should return null if a weak reference can't be resolved.
Component: Untriaged → XPConnect
Product: Firefox → Core
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INACTIVE → ---
See Also: → 1582600
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.