One JS error, Two Warnings in 17.0.2

[GWild55]

Just read there's a better method for reporting bugs: BugZilla... does that also apply to Thunderbird?

These happen just about every mail send or fetch... with 17 and 17.02 having occasional negotiation issues with my server (yet to capture the salient facts there).

=========
Timestamp: 1/9/2013 1:16:33 AM
Error: [Exception... "'Component is not available' when calling method: [nsIActivityManager::removeActivity]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///modules/activity/pop3Download.js :: <TOP_LEVEL> :: line 124" data: no]
Source File: resource:///modules/activity/pop3Download.js
Line: 124

==========
Timestamp: 1/9/2013 1:12:51 AM
Warning: Use of attributes' nodeValue attribute is deprecated. Use value instead.
Source File: chrome://messenger/content/messengercompose/MsgComposeCommands.js
Line: 3993

=========
Timestamp: 1/9/2013 1:22:11 AM
Warning: XUL box for _moz_generated_content_before element contained an inline #text child, forcing all its children to be wrapped in a block.
Source File: chrome://messenger/content/messenger.xul
Line: 0

<?xml version="1.0"?>

<?xml-stylesheet href="chrome://messenger/skin/mailWindow1.css" type="text/css"?>
<?xml-stylesheet href="chrome://gloda/content/glodacomplete.css" type="text/css"?>
<?xml-stylesheet href="chrome://messenger/content/tabmail.css" type="text/css"?>
<?xml-stylesheet href="chrome://messenger/skin/tabmail.css" type="text/css"?>

<?xul-overlay href="chrome://communicator/content/utilityOverlay.xul"?>
<?xul-overlay href="chrome://messenger/content/msgHdrViewOverlay.xul"?>
<?xul-overlay href="chrome://messenger/content/mailWindowOverlay.xul"?>
<?xul-overlay href="chrome://messenger/content/extraCustomizeItems.xul"?>
<?xul-overlay href="chrome://messenger/content/mailOverlay.xul"?>
<?xul-overlay href="chrome://messenger/content/editContactOverlay.xul"?>
<?xul-overlay href="chrome://messenger/content/specialTabs.xul"?>
<?xul-overlay href="chrome://messenger/content/webSearchTab.xul"?>
<?xul-overlay href="chrome://messenger/content/quickFilterBar.xul"?>

<!DOCTYPE window [
<!ENTITY % brandDTD SYSTEM "chrome://branding/locale/brand.dtd" >
%brandDTD;
...

[LoudNoise]

If it turns out to be an actual bug then it should be reported. However, we are far from identifying if it is a bug and, if it is, what is causing it. It much better to discuss it here first.

[GWild55]

The JS line 124 error is quite consistent - there fore repeatable. The warnings are more fluid and seem to dance around in the code.

Just opening the app causes six warnings: I have eight accounts I am checking; three of them do not have top level folders... so the three dupe warnings might be related (and I've asked in another thread how to make new top level folders - without response). No errors when starting the app. The error occurs when using the menu bar Get Mail button.

Any suggestion on how to ferret out the JS error? A troubleshooting FAQ I've overlooked (aka not searched diligently for)?

Timestamp: 1/9/2013 8:50:39 AM
Warning: Error in parsing value for 'padding-bottom'. Declaration dropped.
Source File: chrome://messenger/skin/messenger.css
Line: 401

Timestamp: 1/9/2013 8:50:39 AM
Warning: XUL box for _moz_generated_content_before element contained an inline #text child, forcing all its children to be wrapped in a block.
Source File: chrome://global/content/bindings/toolbar.xml
Line: 276
(occurs three times)

Timestamp: 1/9/2013 8:50:39 AM
Warning: Use of Mutation Events is deprecated. Use MutationObserver instead.
Source File: chrome://messenger/content/msgMail3PaneWindow.js
Line: 944

Timestamp: 1/9/2013 8:50:40 AM
Warning: XUL box for _moz_generated_content_before element contained an inline #text child, forcing all its children to be wrapped in a block.
Source File: chrome://messenger/content/messenger.xul
Line: 0

Timestamp: 1/9/2013 8:55:40 AM
Error: [Exception... "'Component is not available' when calling method: [nsIActivityManager::removeActivity]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///modules/activity/pop3Download.js :: <TOP_LEVEL> :: line 124" data: no]
Source File: resource:///modules/activity/pop3Download.js
Line: 124

[GWild55]

Well, the JS error went away when I reattached the email accounts to account specific top level folders instead of deferring them to Local Folders. So it is a reproducible bug, something that should be fixed... but lower priority.

The warnings just show bad craftsmanship on someone's part; deprecated code and such. Probably making some obscure feature not work right... since it isn't affecting how I use the app, guess I'll say so long and thanks for all the fish... aka: not worry about them.