Closed Bug 1173867 Opened 10 years ago Closed 10 years ago

Irregular Timeout of tabbrowser.xml

Categories

(Firefox :: Tabbed Browser, defect)

38 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: shiyaru900, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150525141253 Steps to reproduce: Uncertain of exact recreation conditions; sometimes happens during longer Mozilla sessions, other times happens within half an hour of use. It seems to be more common when a YouTube video is running in another tab, though that might be just fresher memory of recent events. Only consistency is that it occurs when I attempt to close a tab. I currently have AdBlock Plus 2.6.9.1-signed, ChatZilla 0.9.91.1.1-signed, CoolPreviews 4.6, Download Status Bar 12.3.0.1-signed, and Personas Plus 1.7.3.1-signed installed as extensions. I have OpenH264 Video Codec provided by Cisco Systems, Inc. 1.4, Primetime Content Decryption Module proveded by Adobe Systems, Incorporated 10, Shockwave Flash 17.0.0.188, Unity Player 4.5.5.37569, Adobe Acrobat 11.0.11.18, Google Update 1.3.27.5, Java Deployment Toolkit 8.0.250.18 11.25.2.18, Java(TM) Platform SE 8 U25 11.25.2.18, NVIDIA 3D Vision 7.17.13.4052, NVIDIA 3D VISION 7.17.13.4052, and WacomTabletPlugin 2.1.0.7 installed as plugins. I don't think any of the above extensions or plugins are involved, but just in case I figured I should add it in. Actual results: Upon close attempt, Firefox stops responding; after a brief pause (~20 seconds, I'd guess), an error pops up stating that chrome://browser/content/tabbrowser.xml:#### stopped working; the exact line number varies, but I've seen it range from 1500-3200 at least. If I choose to continue the script, it fails to continue and the error box returns immediately. If I choose to stop the script, then I cannot close any tabs (though opening them works fine). I managed to have the browser console open during the last glitch, and it reported the following: --- 12:04:39.005 A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'? See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise Date: Thu Jun 11 2015 12:04:34 GMT-0500 (Central Standard Time) Full Message: TypeError: this.doc is undefined Full Stack: Toolbox.prototype.selectTool@resource://gre/modules/commonjs/toolkit/loader.js -> resource:///modules/devtools/framework/toolbox.js:1050:9 DevTools.prototype.showToolbox/hostPromise<@resource:///modules/devtools/gDevTools.jsm:404:18 Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:867:23 this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:746:7 this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:688:37 DT_setSlowScriptDebugHandler/debugService.activationHandler@resource:///modules/devtools/gDevTools.jsm:908:9 _endRemoveTab@chrome://browser/content/tabbrowser.xml:2193:17 _endRemoveTab@chrome://browser/content/tabbrowser.xml:2216:17 removeTab@chrome://browser/content/tabbrowser.xml:2049:15 onxblclick@chrome://browser/content/tabbrowser.xml:4947:1 1 toolbox.js:1050:0 --- I'm unsure if this is related, but I'm getting repeated versions of the following error as well, both in clusters of 4-7 and as repeated individual errors: --- 12:03:13.823 NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITaskbarTabPreview.invalidate]1 WindowsPreviewPerTab.jsm:406:0 --- Expected results: Tab closes without note.
Hey Shiyaru, Thank you for reporting this. Are you still having the same issue in the latest version ?
Component: Untriaged → Tabbed Browser
Flags: needinfo?(shiyaru900)
Hey Abe, No, I haven't had the issue in my experience with version 42.0. Hopefully it'll stay that way; if not, I'll be sure to report it again!
Flags: needinfo?(shiyaru900)
Works for me and the reporter. Feel free to reopen it if it reporuduces in the latest build.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.