User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100104 SeaMonkey/2.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100104 SeaMonkey/2.0.2 When opening the cookie manager (Tools/Cookie Manager/Manage Stored Cookies) Seamonkey will eat 100% of cpu for over a minute or so. I think this started with SM 2.0 and remains with 2.0.2. This is a 3Ghz Celeron D with 2G ram running XP with service packs. Reproducible: Always Steps to Reproduce: 1.Manage Stored Cookies 2. 3. Actual Results: SM consumes 100% of cpu cycles for over 1 minute then returns to normal behavior. Expected Results: Expect it to skip the hi cpu consumption.

How many stored cookies does your browser have? Please create a new profile and test the time to open den Cookie Manager in that profile.

Approximately 350 cookies. While scrolling through the list to count them SM went into a 100% cpu cycle for about 10-15 seconds. I'll report again after creating a new profile as requested.

Can you try and reproduce with SeaMonkey v2.0.4 ? Please try in Safe mode ( http://kb.mozillazine.org/Talk:Safe_Mode#Safe_Mode_in_SeaMonkey_2 ), or with a new profile ( http://kb.mozillazine.org/Profile_Manager#Creating_a_new_profile ).

Things seem to have improved with 2.04. I just loaded the cookie manager and it took approximately 16 seconds (vs about 3 times that before) of 100% cpu between clicking on manage cookies and the manager loading. Then clicking on the scroll bar for the list of cookies cpu went 100% for about 5-6 seconds before scrolling started. No noticeable delay if i then search for cookies etc at that point. Launching SeaMonkey in Safe Mode made no apparent difference.

Does this still happen in cookie manager / data manager?

No problems with cookie manager and SM 2.4.1