311663 - high cpu after opening compose and thunderbird does not shut down

Status: RESOLVED DUPLICATE of bug 311223

(Thunderbird :: Message Compose Window, defect)

Description

[Wayne Mery (:wsmwk)]

version 1.6a1 (20051007)

normal CPU and all OK until compose window is opened. Then high cpu in the range
18-50% and higher. Also, TB process doesn't end at TB shutdown - high cpu
continues and process must be killed.  

doesn't happen with 20050928 trunk (if it did, I'd suggest bug 311446 may be
related)

If I don't open compose in 20051007, I get the same shutdown error as I get with
20050928 and builds going back to at least 20050917

I can't confirm, but I thought autocomplete wasn't working the first time I
started this build (but it is working now).


FWIW, javascript console as follows - but exact same messages appear with 20050928 

Error: not well-formed
Source File:
file:///C:/Documents%20and%20Settings/Wayne/Application%20Data/Thunderbird/Profiles/srv1to0w.default/Mail/News%20&%20Blogs/feeds.rdf
Line: 5, Column: 18
Source Code:
  <urn:forumzilla:feed
RDF:about="http://lists.slimdevices.com/archives/announce/rss.xml"

Error: not well-formed
Source File:
file:///C:/Documents%20and%20Settings/Wayne/Application%20Data/Thunderbird/Profiles/srv1to0w.default/Mail/News%20&%20Blogs/feeditems.rdf
Line: 5, Column: 34
Source Code:
                   urn:forumzilla:stored="true"

Error: [Exception... "Component returned failure code: 0x8000ffff
(NS_ERROR_UNEXPECTED) [nsIRDFService.GetDataSourceBlocking]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://messenger-newsblog/content/utils.js :: getItemsDS :: line 222"  data: no]
Source File: chrome://messenger-newsblog/content/utils.js
Line: 222

Error: not well-formed
Source File:
file:///C:/Documents%20and%20Settings/Wayne/Application%20Data/Thunderbird/Profiles/srv1to0w.default/Mail/News%20&%20Blogs/feeditems.rdf
Line: 5, Column: 34
Source Code:
                   urn:forumzilla:stored="true"

Error: [Exception... "Component returned failure code: 0x8000ffff
(NS_ERROR_UNEXPECTED) [nsIRDFService.GetDataSourceBlocking]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://messenger-newsblog/content/utils.js :: getItemsDS :: line 222"  data: no]
Source File: chrome://messenger-newsblog/content/utils.js
Line: 222

Error: not well-formed
Source File:
file:///C:/Documents%20and%20Settings/Wayne/Application%20Data/Thunderbird/Profiles/srv1to0w.default/Mail/News%20&%20Blogs/feeditems.rdf
Line: 5, Column: 34
Source Code:
                   urn:forumzilla:stored="true"

Error: [Exception... "Component returned failure code: 0x8000ffff
(NS_ERROR_UNEXPECTED) [nsIRDFService.GetDataSourceBlocking]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://messenger-newsblog/content/utils.js :: getItemsDS :: line 222"  data: no]
Source File: chrome://messenger-newsblog/content/utils.js
Line: 222

Error: not well-formed
Source File:
file:///C:/Documents%20and%20Settings/Wayne/Application%20Data/Thunderbird/Profiles/srv1to0w.default/Mail/News%20&%20Blogs/feeditems.rdf
Line: 5, Column: 34
Source Code:
                   urn:forumzilla:stored="true"

Error: [Exception... "Component returned failure code: 0x8000ffff
(NS_ERROR_UNEXPECTED) [nsIRDFService.GetDataSourceBlocking]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://messenger-newsblog/content/utils.js :: getItemsDS :: line 222"  data: no]
Source File: chrome://messenger-newsblog/content/utils.js
Line: 222

Comment 1

[Hermann Schwab]

(In reply to comment #0)
> version 1.6a1 (20051007)
> 
> normal CPU and all OK until compose window is opened. Then high cpu in the range
> 18-50% and higher. Also, TB process doesn't end at TB shutdown - high cpu
> continues and process must be killed.  
> 
> doesn't happen with 20050928 trunk (if it did, I'd suggest bug 311446 may be
> related)

Looking at timeframe and symptoms this seems to be a dupe of
Bug 311223 Mail or news composition (new or reply) grabs 85-95% system resources.

I don't know about the rest of your bug. Bug 311223 got a wallpaper checkin
yesterday, so todays nightly (and Tinderbox builds 2005100720 and later) don't
show that CPU load I observed on 
Bug 310854 Browser generates CPU load while idle
Bug 311223 is still open for the real fix. Please recheck your bug with a newer
build.

Comment 2

[David :Bienvenu]

*** Bug 311728 has been marked as a duplicate of this bug. ***

Comment 3

[Wayne Mery (:wsmwk)]

(In reply to comment #1)
> Bug 311223 is still open for the real fix. Please recheck your bug with a newer
> build.

WFM with 20051008 build after checkin noted above


*** This bug has been marked as a duplicate of 311223 ***