Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
Hartmut Figge schrieb: First i had posted about this issue several weeks ago in 4abf7628.4060...@hfigge.myfqdn.de, also dcsm.n-b. And later i thought that some numbers would be nice. *g* As it looks like we have a real problem with a reproducible and logically explainable cause, do we also have a bug report for that? And do we know if TB3 has the same issue? In any case, thanks for finding this out, those points above should IMHO be the next steps if they haven't been done already. Also, it might make sense to do a release notes entry for this under Known Issues, we'd need a text and the bug reference for that. Robert Kaiser ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
On 10/31/2009 07:13 PM, Hartmut Figge wrote: NoOp: I have 'Check for...' turned off for all news servers, but have grown accustom to the high cpu when checking my gmane.org newsgroups in 2.0 where I have at least 25 subscribed groups. Yes, it doesn't matter if you check manually or if that si done automatically. When I first open the server (click the right triangle next to the server name), cpu skyrockets all things mozilla pause. I can confirm that this does not happen when doing the same from my 1.1.18 (linux windows). I have already given the time frame. First the problem could be avoided by backing out 'Patch, version 1.1' from https://bugzilla.mozilla.org/show_bug.cgi?id=311774. 4ac0a452.4070...@hfigge.myfqdn.de. Ok I give, what specifically is: 4ac0a452.4070...@hfigge.myfqdn.de ? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
NoOp: On 10/31/2009 07:13 PM, Hartmut Figge wrote: I have already given the time frame. First the problem could be avoided by backing out 'Patch, version 1.1' from https://bugzilla.mozilla.org/show_bug.cgi?id=311774. 4ac0a452.4070...@hfigge.myfqdn.de. Ok I give, what specifically is: 4ac0a452.4070...@hfigge.myfqdn.de ? Don't understand the question. Are you asking about, what a MID is? Or for the content of posting to which the MID is pointing? Well, using the MIDF on the MID one can get the Posting e.g. in Goggle. http://groups.google.com/group/de.comm.software.mozilla.nightly-builds/msg/159965120a124f64 The MIDF is one of two add-ons i cannot live without. The other one is Mnenhy. *g* Hartmut ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
On 11/01/2009 04:12 PM, Hartmut Figge wrote: NoOp: On 10/31/2009 07:13 PM, Hartmut Figge wrote: I have already given the time frame. First the problem could be avoided by backing out 'Patch, version 1.1' from https://bugzilla.mozilla.org/show_bug.cgi?id=311774. 4ac0a452.4070...@hfigge.myfqdn.de. Ok I give, what specifically is: 4ac0a452.4070...@hfigge.myfqdn.de ? Don't understand the question. Are you asking about, what a MID is? Or for the content of posting to which the MID is pointing? The Message ID: 4ac0a452.4070...@hfigge.myfqdn.de I don't use google groups et al; nor do many others. Well, using the MIDF Obviously you are not from Malaysia :-) http://acronyms.thefreedictionary.com/MIDF on the MID one can get the Posting e.g. in Goggle. http://groups.google.com/group/de.comm.software.mozilla.nightly-builds/msg/159965120a124f64 Blah - it's Message-ID (according to the header), as in Message-ID: 4aee23d7.2050...@hfigge.myfqdn.de The link works, but it's really a post on news://de.comm.software.mozilla.nightly-builds/ and why assume anyone uses google group eh? The MIDF is one of two add-ons i cannot live without. The other one is Mnenhy. *g* Never used Mnenhy. But simply posting a 'Message-ID' in a bug report probably isn't going to get much mileage. My suggestion would be to be less lazy (:-)) and: 1) post a link to the msg as you've done above, and/or 2) just post what you are talking about. For others interested; here is the english translation (provided by google) of Harmut's post with some snippage: http://groups.google.com/group/de.comm.software.mozilla.nightly-builds/msg/159965120a124f64 quote ... Hartmut Figge View profile Translate to English Translated (View Original) Hartmut Figge: Alfred Peters Through Check-Out confirmed: Yes, the patch is to blame! 'You're so terribly active. I hope that I succeed in my conscience to keep in check. It is not. There was such an insidious gnawing constantly in the background because of suspicious matches. Sigh. So, after this patch Kick out the problem with that is CPU load removed. Hartmut -- Usenet-ABC-Wiki http://www.usenet-abc.de/wiki/ Of users for user :-) Hide options Sep 28, 7:56 am Newsgroups: de.comm.software.mozilla.nightly-builds From: Hartmut Figge h.fi...@gmx.de Date: Mon, 28 Sep 2009 13:56:02 +0200 Local: Mon, Sep 28 2009 7:56 am Subject: Re: Leeres Artikelfenster durch Aktualisierung Reply | Reply to author | Forward | Print | View thread | Show original | Report this message | Find messages by this author Hartmut Figge: Alfred Peters Through Check-Out confirmed: Yes, the patch is to blame! 'You're so terribly active. I hope that I succeed in my conscience to keep in check. It is not. There was such an insidious gnawing constantly in the background because of suspicious matches. Sigh. So, after this patch Kick out the problem with that is CPU load removed. Hartmut -- Usenet-ABC-Wiki http://www.usenet-abc.de/wiki/ Of users for user :-) /quote And after all of that, I'm not sure that I understand anything :-) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
NoOp: On 11/01/2009 04:12 PM, Hartmut Figge wrote: Well, using the MIDF Obviously you are not from Malaysia :-) http://acronyms.thefreedictionary.com/MIDF :-P http://messageidfinder.mozdev.org/ But this one will not work on SM2. I had to fix it for my personal needs. And there will be no official new version AFAIK. The functionality may be transferred to a future version of Mnenhy, though. Here is a screenshot of the menu of the MIDF. http://www.triffids.de/pub/screenshot/mi091018.png (34 KB) it's Message-ID (according to the header), as in Message-ID: 4aee23d7.2050...@hfigge.myfqdn.de The link works, but it's really a post on news://de.comm.software.mozilla.nightly-builds/ Right. and why assume anyone uses google group eh? You have to have a method of finding this posting using the MID. One possibility is the advanced search of Google. A better one is to interrogate a newsserver directly. Sometimes Google fails to find a posting. The MIDF is one of two add-ons i cannot live without. The other one is Mnenhy. *g* Never used Mnenhy. But simply posting a 'Message-ID' in a bug report probably isn't going to get much mileage. Mhm, i felt responsible to add some comment ... My suggestion would be to be less lazy (:-)) ... but there is this point. *g* and: 1) post a link to the msg as you've done above, The result would still point to a text in German. and/or 2) just post what you are talking about. Much could be done better. More investigation, determining the time frame, providing a patch. But luckily i am only a user and not a devel. So i can stay with Wizardry 7, at the moment. :) Hartmut ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
On Sun, 01 Nov 2009 16:28:48 -0800, NoOp wrote: On 11/01/2009 04:12 PM, Hartmut Figge wrote: NoOp: The Message ID: 4ac0a452.4070...@hfigge.myfqdn.de I don't use google groups et al; nor do many others. Well, using the MIDF Obviously you are not from Malaysia :-) http://acronyms.thefreedictionary.com/MIDF Well I am, so that reference by Hartmut confused me no end. Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. [ ]All hope abandon, ye who enjoy tax forms. * TagZilla 0.066.6 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
Philip Chee: On Sun, 01 Nov 2009 16:28:48 -0800, NoOp wrote: On 11/01/2009 04:12 PM, Hartmut Figge wrote: Well, using the MIDF Obviously you are not from Malaysia :-) http://acronyms.thefreedictionary.com/MIDF Well I am, so that reference by Hartmut confused me no end. Didn't know, that the MIDF may be unknown in this NG. ;) Hartmut ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
An update to the reoccuring stalling mystery of SM 2.0 that I posted in detail earlier. After many hours of close observation of the CPU load on the individual CPU cores on the multi-core CPU I am running on, using both the AMD Power Monitor (which displayed individual core load and dynamic core clock speed), as well as the Windows-XP Task Manager PERFORMANCE tab CPU activity graphs. I have noted that whenever the SM 2.0 stalling occurs every few minutes, the CPU load / utilization on one of the 3 cores on the processor reaches nearly full load 100% for a number of seconds (often 10 to 20 seconds), during which time the entire SM 2.0 suite and all its windows will freeze / stall temporarily. This observation has been consistent all this time. To further verify that this symptom and CPU load is contributed ENTIRELY by SM 2.0, I also ran the SYSTINTERALS PROCESS EXPLORER, which I use as a system diagnostic tool from time to time: http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx This utility confirms that the CPU load surge is contributed ENTIRELY by the process listed as seamonkey.exe in the process list of the Process Explorer utility, and not from any other process at all. My system is completely clean of any virus or spyware and is closely monitored at all times. There is also no other utility running in the background and the set up is identical to when I was running all previous SM 1.1.1X releases. When the CPU load surges, Process Explorer's CPU consumption reading for seamonkey.exe surges up to 33.33% (of the entire system's available CPU power), this basically concurs with my observation on the AMD Power Monitor utility which indicates that one of the three cores on this CPU receives a load very close to or at 100% load during the stalling period. SM 2.0 TWEAKS At this point, I am at a loss as to what possible internal function or process inside SM 2.0 could possibly cause what appears to be a massive CPU consumption surge at semi-regular time intervals that could possibly contribute to this. Some internal configuration parameters within ABOUT:CONFIG have been tweaked / tested with no significant improvement. Some of the parameters / actions I have tweaked included: * Disabling browser session restoration function (browser.sessionstore.enabled) * Drastically increasing the browser session save interval (browser.sessionstore.interval) from the default 10 seconds to 300 seconds (5 minutes) * Editing the CRASH REPORTER initialization file CRASHREPORTER.INI so that the Crash Reporter is disabled on start up. * Tweaking the browser cache memory value (browser.cache.memory.capacity), a value which was removed from the PREFERENCES window settings quite some time ago in the Mozilla suite, before Seamonkey. OTHER STRANGE OBSERVATIONS - SM Windows task bar button disappearance One symptom I noticed during the stalling period is when I am scrolling through a displayed e-mail (not in mail composition window). If stalling is occuring and I turn my mouse wheel, the e-mail scrolling does not immediately occur during the stalling period, and the Windows busy mouse pointer icon appears if I try to scroll or simply click inside the e-mail. After the stalling period is over, the e-mail will scroll, BUT - then the TASKBAR BUTTON for the MAIL WINDOW will DISAPPEAR from the Windows taskbar completely. Usually, I will have the browser window and mail window open at the same time, so after this disappearance, I will be left ONLY with the browser window's taskbar button on the taskbar EVEN THOUGH the mail window is still open. In order to restore the mail window taskbar button, I have to flip the focus to the browser window by hitting Ctrl-1, then flip the focus back to the mail window by hitting Ctrl-2. At that point, the Windows taskbar button for the mail window will reappear on the Windows taskbar. I have observed that with SM 1.X or 1.1.XX versions, occasionally I may also lose one of the Windows taskbar buttons for an open SM window. Most often this happens to the mail composition window under SM 1.X because I flip back and forth between browser, mail window and mail composition windows a lot when I use SM, often using the Windows Alt-Tab keyboard shortcut. But with SM 2.0, this is the first time I can consistently trigger the Windows task bar button disappearance by simply doing something while the stalling period is occuring. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
Are you doing updates more than once a day? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
Nope. I always disable all automatic updates for all my software if at all possible, including SM. The release I am currently running is the original release posted on the official Seamonkey project page on the first day it was released. It has not been updated since nor am I aware that there is an update available. I read that the next forthcoming minor revision will be 2.01. It's starting to get quite painful now using SM 2.0 due to the regular stalling, and all available diagnostic tools I have to look at what's going on from outside of the SM application points directly to SM somehow internally causing these CPU load surges. I'm seriously starting to think about putting SM 1.1.18 back on because the SM suite's functionality is an extremely important on my system that I am literally always using when my system is running. Rick Merrill wrote: Are you doing updates more than once a day? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
Hartmut Figge wrote: User: An update to the reoccuring stalling mystery of SM 2.0 that I posted in detail earlier. After many hours of close observation of the CPU load on the individual CPU cores on the multi-core CPU I am running on, using both the AMD Power Monitor (which displayed individual core load and dynamic core clock speed), as well as the Windows-XP Task Manager PERFORMANCE tab CPU activity graphs. I have noted that whenever the SM 2.0 stalling occurs every few minutes, the CPU load / utilization on one of the 3 cores on the processor reaches nearly full load 100% for a number of seconds (often 10 to 20 seconds), during which time the entire SM 2.0 suite and all its windows will freeze / stall temporarily. This observation has been consistent all this time. That reminds me on4ae69e4e.60...@hfigge.myfqdn.de in de.comm.software.mozilla.nightly-builds. For me the increasing load occurs every time when the newsservers are updated due to 'Check for new messages every [ ] minutes'. Or at the start of MailNews. First i had posted about this issue several weeks ago in 4abf7628.4060...@hfigge.myfqdn.de, also dcsm.n-b. And later i thought that some numbers would be nice. *g* http://www.triffids.de/pub/sm/2.0/load/smlog.txt In the lines starting with 'top' the relative time of the measurement can be seen. Every second. Interesting is the number below %CPU. Haven't investigated further. But you are not alone, it seems. ;) Hartmut Thanks very much for your reply. Finally - an explanation for the first time on this mystery that makes a lot of sense. I did already notice that when loading newsgroups or downloading large number of newgroup headers, or when removing expired newsgroup articles, that considerable CPU load results. It just never occured to me that the auto check newsgroup messages would cause this sort of serious load on the entire suite to the point of stalling. I've since inspected the auto check server settings for the several newsgroup servers I have set up with SM 2.0 (all newsgroups of which were successfully migrated manually from SM 1.X) and found that there were 2 news servers (the Mozilla server included) that had auto check message function on. From what I remember, I had these preferences on in SM 1.X as well but never appeared to encounter the CPU load issue in SM 1.X and didn't think much about it when migrating to SM 2.0. However, after disabling the auto check message function, virtually all of the stalling appeared to have disappeared. I have only used SM 2.0 for about an hour since this making this adjustment, but overall everything is working a lot more smoothly though there is still the occasional minor stuttering of video playback (I tried only Flash FLV playback in web pages so far), and Flash FLV video playback within a web page appears to still generate more CPU load compared to SM 1.X, but the demands are still well within available CPU power from my multi-core CPU. One thing I have never been too clear about the newsgroup function on the Mozilla suite / Seamonkey - if I have a newsgroup server collapsed in the news folder pane, then the newsgroup server is NOT accessed UNTIL I either highlight the news server or open it and highlight one of the newsgroups hosted on the server, is that correct? Normally, I do not access newsgroups much and would like to keep newsgroup functions CPU loads to zero or minimal levels. If you or anyone can clarify this point about the newgroup function, I would appreciate it. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
User: One thing I have never been too clear about the newsgroup function on the Mozilla suite / Seamonkey - if I have a newsgroup server collapsed in the news folder pane, then the newsgroup server is NOT accessed UNTIL I either highlight the news server or open it and highlight one of the newsgroups hosted on the server, is that correct? Unfortunately not true for at least SM2.0 nightlies of the last months and now SM2.1. It became obvious with the increase of the load during the fetch of new postings. Btw, the time frame for this is h...@e675 ~ $ fenster 0909240813-0909251108 2009-09-23 23:13:00 PDT 2009-09-25 02:08:00 PDT as i had written in 4ac096d3.7030...@hfigge.myfqdn.de At the moment the collapsed state of a newsserver is not honored when new postings are automatically fetched or at the start of MailNews. All what matters are the two checkboxes for 'Check for ...' under Server Settings. Well, this is a horrible waste of bandwidth and useless also. If a newsserver is collapased, why should he care about new postings? I had lamented strongly about this issue in dcsm. *g* Hartmut ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
Hartmut Figge wrote: User: One thing I have never been too clear about the newsgroup function on the Mozilla suite / Seamonkey - if I have a newsgroup server collapsed in the news folder pane, then the newsgroup server is NOT accessed UNTIL I either highlight the news server or open it and highlight one of the newsgroups hosted on the server, is that correct? Unfortunately not true for at least SM2.0 nightlies of the last months and now SM2.1. It became obvious with the increase of the load during the fetch of new postings. Btw, the time frame for this is h...@e675 ~ $ fenster 0909240813-0909251108 2009-09-23 23:13:00 PDT 2009-09-25 02:08:00 PDT as i had written in4ac096d3.7030...@hfigge.myfqdn.de At the moment the collapsed state of a newsserver is not honored when new postings are automatically fetched or at the start of MailNews. All what matters are the two checkboxes for 'Check for ...' under Server Settings. Well, this is a horrible waste of bandwidth and useless also. If a newsserver is collapased, why should he care about new postings? I had lamented strongly about this issue in dcsm. *g* Hartmut Thanks again for your reply. Do you have any confirmation whether the collapsed news server state in SM 1.X resulted in the application from skipping of the news server fetch operation? If yes, then this would appear to be a regression of a sensible logic that should be in place. Certainly it caused me a lot of wasted time and grief shortly after installation of SM 2.0 to try and find out why the hell the application was having regular CPU load surges to the point of bringing the entire application to its knees. One thing that seems to be contradicting your assessment though, is that I have one news server group set up whereby when it is accessed, it will prompt me for a password. However, when I have that newsgroup collapsed, the password is never prompted, so presumably this implies that news server is never accessed / checked. This would seem contradictory to your assessment that the news server is checked even if the news server group was collapsed. So I am not sure about this point. I did not view the messages in the links to other German newsgroups you mentioned earlier, because I had presumed they might be in German language. But if it is English I would be interested to check it out. I agree that it is a useless waste of bandwidth and also more importantly, a completely avoidable problem with regards to CPU load and application thread load. It would be nice if someone who has close involvement in the newsgroup logic development on SM 2.0 provide some insight / clarification on this issue. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
User: Thanks again for your reply. Do you have any confirmation whether the collapsed news server state in SM 1.X resulted in the application from skipping of the news server fetch operation? Too long ago for me. I am using self compiled nightlies for many years and SM1, well, after deleting older builds my archive now begins with a SM1.5a from 060201. ;) One thing that seems to be contradicting your assessment though, is that I have one news server group set up whereby when it is accessed, it will prompt me for a password. However, when I have that newsgroup collapsed, the password is never prompted, so presumably this implies that news server is never accessed / checked. This would seem contradictory to your assessment that the news server is checked even if the news server group was collapsed. So I am not sure about this point. That behavior is true for newsservers when 'Check for ...' under Server Settings is not checked. I have to to so for some newsservers because otherwise the collapsed state is nor respected. *grrr* I did not view the messages in the links to other German newsgroups you mentioned earlier, because I had presumed they might be in German language. So it is. I'm writing much in the german newsgroups of mozilla. But in news.mozilla.org, well, that's hard work for me. But if it is English I would be interested to check it out. There is a translator in google. :-P I agree that it is a useless waste of bandwidth and also more importantly, a completely avoidable problem with regards to CPU load and application thread load. With regard of not respecting the collapsed state it is a waste, but on the other other hand there is now a very nice feature which may be related to the load. While reading a NG new postings now appear automatically. No need, to trigger that. Very nice. :) Oh, i am using View-Threads-Threads with Unread. Hartmut ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
On 10/31/2009 04:58 PM, Hartmut Figge wrote: User: One thing I have never been too clear about the newsgroup function on the Mozilla suite / Seamonkey - if I have a newsgroup server collapsed in the news folder pane, then the newsgroup server is NOT accessed UNTIL I either highlight the news server or open it and highlight one of the newsgroups hosted on the server, is that correct? Unfortunately not true for at least SM2.0 nightlies of the last months and now SM2.1. It became obvious with the increase of the load during the fetch of new postings. Btw, the time frame for this is h...@e675 ~ $ fenster 0909240813-0909251108 2009-09-23 23:13:00 PDT 2009-09-25 02:08:00 PDT as i had written in 4ac096d3.7030...@hfigge.myfqdn.de At the moment the collapsed state of a newsserver is not honored when new postings are automatically fetched or at the start of MailNews. All what matters are the two checkboxes for 'Check for ...' under Server Settings. Well, this is a horrible waste of bandwidth and useless also. If a newsserver is collapased, why should he care about new postings? I had lamented strongly about this issue in dcsm. *g* Hartmut I have 'Check for...' turned off for all news servers, but have grown accustom to the high cpu when checking my gmane.org newsgroups in 2.0 where I have at least 25 subscribed groups. Perhaps I got used to it in testing 2.x pre/nightly/alpha/beta etc. When I first open the server (click the right triangle next to the server name), cpu skyrockets all things mozilla pause. I can confirm that this does not happen when doing the same from my 1.1.18 (linux windows). This is a valid issue. But I've not bothered searching for a bug report yet, but would appreciate it if perhaps you know of one already opened? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
NoOp: I have 'Check for...' turned off for all news servers, but have grown accustom to the high cpu when checking my gmane.org newsgroups in 2.0 where I have at least 25 subscribed groups. Yes, it doesn't matter if you check manually or if that si done automatically. When I first open the server (click the right triangle next to the server name), cpu skyrockets all things mozilla pause. I can confirm that this does not happen when doing the same from my 1.1.18 (linux windows). I have already given the time frame. First the problem could be avoided by backing out 'Patch, version 1.1' from https://bugzilla.mozilla.org/show_bug.cgi?id=311774. 4ac0a452.4070...@hfigge.myfqdn.de. But strangely this was not longer true as i tried that some time later. I could have investigated further, but, did i mention already that i'm lazy? ;) Hartmut -- Usenet-ABC-Wiki http://www.usenet-abc.de/wiki/ Von Usern fuer User :-) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
On 10/31/2009 07:13 PM, Hartmut Figge wrote: NoOp: I have 'Check for...' turned off for all news servers, but have grown accustom to the high cpu when checking my gmane.org newsgroups in 2.0 where I have at least 25 subscribed groups. Yes, it doesn't matter if you check manually or if that si done automatically. When I first open the server (click the right triangle next to the server name), cpu skyrockets all things mozilla pause. I can confirm that this does not happen when doing the same from my 1.1.18 (linux windows). I have already given the time frame. First the problem could be avoided by backing out 'Patch, version 1.1' from https://bugzilla.mozilla.org/show_bug.cgi?id=311774. 4ac0a452.4070...@hfigge.myfqdn.de. But strangely this was not longer true as i tried that some time later. Thanks for the link. I could have investigated further, but, did i mention already that i'm lazy? ;) Yes, on multiple occasions :-) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
NoOp wrote: When I first open the server (click the right triangle next to the server name), cpu skyrockets all things mozilla pause. I can confirm that this does not happen when doing the same from my 1.1.18 (linux windows). Strangely also, when the newsgroup auto check messages function is enabled, I found that the web browser URL field auto complete function is extremely slow. Previously in SM 1.X for Windows, the auto complete search is almost instantaneous when I type in a partial match of a previously visited URL. But for all the time up until I disabled the newsgroup auto check message function in SM 2.0, I found that the browser URL field auto complete function was extremely slow and I had to wait a number of seconds before matches would be displayed. Now with the newsgroup auto check messages function turned off in SM 2.0, the browser URL auto complete search function is as fast as what I had in SM 1.X. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Feedback to Seamonkey developers - SM 2.0 high CPU resource consumption bursts
Update to the original feedback post I made earlier - After extensive monitoring of individual core load on the multi-core CPU while playing back many different Flash FLV videos, I can positively confirm that virtually all of the time, Flash FLV playback using the exact same Flash plug-in that I previously used on SM 1.X, requires SIGNIFICANTLY more CPU power and generates much more load on the CPU cores when played back under SM 2.0 compared to playing back on SM 1.X. The core load percentage as well as the individual core clock speed as adjusted through dynamic throttling, clearly confirms this. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
