• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

Seamonkey 99.9% CPU locks or crashes

Started by OriAl, 2010.08.21, 20:33:10

Previous topic - Next topic

OriAl

I cannot use Seamonkey or Firefox in eCS 1.2.  The CPU is always pegged at 99.9%, and page loading is extremely slpw, or the app locks and must be closed, or crashes.  I don't know what to do about this.  It wasn't problem with SM 1.1x or FF 2.x.

jep

Hello,

I had similar problems... due to I opened many tabs and restored them after every restart of the web browser. I think it caused constant writes to sessionstore.js, so you may try to alter the setting for how often it should write to sessionstore.js and see if it helps you.

Beware of the warning, I'm not responsible if you change some setting that cause you problems. It your own fault!

You can try the following:
Entry field: Address bar
Type: about:config
Read the text and confirm that you take responsibility for the problems you may cause as you change settings.
Button: I promise, I will be careful!
Entryfiled: Filter:
Type: sessionstore
Row: browser.sessionstore.interval
Doubleclick: browser.sessionstore.interval
Change to: 30000 (equals 30 seconds = 30 000 milliseconds)

You may also try to see if a lower value for e.g. browser.sessionstore.max_tabs_undo improve performance.

Read more about sesstionstore

=======8<-------------
Background

Firefox 2.0 introduces a built-in Session Restore feature, allowing the user to continue browsing from where they left off if browser restarts. This preference controls how often information about the current session is saved to the profile.

Possible values and their effects

A positive integer indicating the number of milliseconds between session saving operations. (Default is 10000, or 10 seconds)
------------->8=======

warpcafe

Hi OriAl,

I suppose you tried "-safemode" (starting FFx in safemode to rule out any extensions/plugins cause the problem) ?

Cheers,
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

OriAl

I tried safemode.  Same problem.

This is using eCS 1.2.  I

RobertM

OH!!!! I had this problem! Hope this is the same one for you. Innotek Font Engine was causing it. FF 2.x and downwards used (or could use) it to render fonts nicer. When I went to the later builds of FF (the 3.x builds), I had to disable IFE or it would eat CPU, and eventually things would grind to a halt.

Someplace here there is a thread on it. Basically, if you have neat anti-aliased fonts in FF2, then FF3 may be double "rendering" the fonts via it's internal renderer and then IFE.

Easy fix: rename firefox.exe to firefox3.exe (or any name that is not an executable name linked to IFE). More complex fix (though possibly easier in the long run, as you dont have to keep renaming the exe every time you upgrade) is detailed someplace on the forums, and involves removing an ini/registry entry that tells IFE to handle firefox font rendering.

Hope that helps...

If this is not the case, let us know so we can dig deeper.

-Rob


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


Pete

Hi

There are several places to look in the Registry:-

HKEY_CURRENT_USER\Software\InnoTek\InnoTek Font Engine\Applications
HKEY_LOCAL_MACHINE\Software\InnoTek\InnoTek Font Engine\Applications
HKEY_USERS\.default\Software\InnoTek\InnoTek Font Engine\Applications

if using Seamonkey v2 or Firefox v3 simply delete the relevant filename (eg seamonkey.exe) or change it to Disabled by setting the Data value to 0. I would guess this also applies to later builds of Thunderbird.

Regards

Pete

RobertM

Thanks Pete! Sorry I couldnt come up with that info... doing some web testing (meaning making sure crap works in IE) and thus stuck on a Windows machine today... so no access to that info for me at the moment.

Rob


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


OriAl

Forgot this was here <sheepish look.>  Still having the same problems.  How do I access the registry?

Another issue - when using eCS (1.2), MR/2 ICE 2.67 and Seamonkey (currently 2.08) will not download large e-mail messages.  Both apps time out, and that happens any time I try to download mail with them (I don't try them at the same time.)  I have to boot to XP to get my mail directly from comcast.net, from where I can move the large messages to Saved or delete them, then I can boot eCS and get the smaller mails.  SM is not set for any message size limit, nor is ICE (doesn't appear to have such a. setting.)  If I didn't have an XP, I'd be in real trouble, as eCS browsers aren't compatible with Comcast's Smartzone mail page.

Any ideas?

Thank you,

Al


Pete

Hi

Local System -> System Setup -> Registry Editor aka \OS2\SYSTEM\REGEDIT2.EXE

No idea on the email problem... might be worth asking in the mozilla newsgroup.

Regards

Pete


warpcafe

HI,

I remember I read the same problem description (large email D/L) somewhere, some time back. Not sure what the problem was. In any case - is this related to emails only or does it also occur when doing large downloads in general? Perhaps it's an MTU issue? NIC driver problem in general?
If it's with email only, it might be worth checking FAQ, customer support or forums at comcast... maybe you can find this issue among users running Linux flavors...

Regards,
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

OriAl

Warpcafe, I have no problem downloading large files using Seamonkey in eCS (for example, I download Seamonkey releases.)  It's only e-mail that has the problem.  As it happens in both Seamonkey and MR/2, it would seem that the issue may not be with the those two mail apps, but possibly something else.  Of course, I know next to nothing, so I'm probably wrong.  The messages download fine to MR/2 Win and Seamonkey in XP, so it doesn't seem to be a Comcast issue.  The Nic driver is for an Intel Pro 10/100 card I've used for who knows how long.

Pete, thank you for the info re the registry.


Al