I haven't seen it do anything like this before... Using the April 7 1999 build (and an edited prefs.js file to use MS Gothic as its font), launching apprunner does very bad things to my Windows 98 system. Within a minute of launch, Symantec Norton System Doctor (the latest version) starts throwing up error messages and quits. Then, Explorer itself starts to display things in the wrong font. The Start menu stops working. You can't quit apprunner, and finally the machine has to be turned off. This kind of behavior is similar to what I'd expect with massive memory leakage, but I can't say for sure what's going wrong. Still investigating. After reboot, everything is OK again until apprunner is launched again.

Actually, this happens when I visit Yahoo! Japan (URL above). May be OK with other sites, not sure.

The 04 07 01 build ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/1999-04-07-01/ was a test build made prior to all the final M4 changes being checked in. cyeh will post a notice with the first M4 candidate is available.

Once cyeh has posted the real M4 candidate I'll revisit this first thing.

Re-assigned to chofmann@netscape.com. Chris, who gets this bug??? Is this what Hyatt and Waterson are working on?

recheck with builds at ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/1999-04-07-11/ this url loads and runs ok on my win95 laptop with the latest. reopen if you still see problems.

Using the second set of April 7 builds, it still wreaks havoc on my system. (I am using Windows 98 with my prefs.js file edited to us the MS Gothic Japanese language font.)

There's something about this page that sucks up gobs of RAM. Using the third build of the day (the 18:00 build) I still run out of RAM and crash horribly at this URL.

bob, can you have one of your guys look at it?

Cata, please take a look at this. Putting this on the M4 radar for now. Is this only Win98? Is it OK on Win95 and NT? Can someone let us use a Win98 set up for running purify. We don't have one in our group.

blee, teruko, could you try to reproduce the problem. thanks

I'm not seeing any problems using NT 4 SP 4. Investigating on Windows 95...

cpratt, can you still reproduce the problem w/o the prefs.js ?

I'm not seeing a problem here at work on my 90 MHz Compaq PC running Windows 98. The problem was seen at home on a Dell Dimension XPS R400 PC. So... I'll try it again from home this afternoon at around 16:00 and let you know. I'm guessing that if this is valid, it's specific to certain hardware...

The page does not have the META tag so my guess is that (if there is no prefs.js) it will just use the latin1 converter without crashing. After adding the tag (which on second reload uses the EUC-JP decoder) on NT40 everything's fine. I wonder what's wrong on Win98?!

This is still very much a problem with the April 9 build on my home Windows 98 PC. It's a Dell Dimension XPS R400 with 224 MB of RAM. I've posted a Dr Watson file at http://schist/snapshot.wlg - a basic snapshot of my system. It's got all kinds of cruft running on it. - Again, I do not have this problem on either machine at work (a H-P running NT or a Compaq running 98).

Using the default seamonkey install, there are NO problems. However, I create a file called "prefs.js" that contains the following information: // Netscape User Preferences // This is a generated file! Do not edit. user_pref("intl.character_set", 260); user_pref("intl.font260.win.fixed_font", "MS Gothic"); user_pref("intl.font260.win.fixed_size", 12); user_pref("intl.font260.win.prop_font", "MS Gothic"); user_pref("intl.font260.win.prop_size", 12); When I copy this in to the x86rel (default) apprunner folder, and restart apprunner, going to that URL wreaks havoc.

Ok, as it seems a very seldom problem and I am unable to fix this without reproducing it, I will mark it as M5 and reassign it back to cpratt. We can revisit it later when we'll be able to reproduce it somehow.

Sounds fine to me. This seems to happen with other Japanese language pages as well, for reasons I don't understand. Is there some profiling tool or other utility I can use to see what's taking up all of the RAM? Any help is appreciated...

It seems that bug 4874 is a duplicate of this one and it has a URL working on NT! I reproduced the problem and checked in a fix. It should go into M4. cpratt, could you please check (when the build is available) if that fixes your problem too? Thanks!

I'll check... but the system that was causing the problems is no more (I upgraded it to NT). So, I can only hope that that fix works... :)

Can't seem to reproduce this (this is possibly due to the fact that the system that exhibited this behaviour no longer exists?). Marking worksforme.

Moving from Apprunner to Other component temporarily whilst don and I set proper component. Apprunner component will be retired/deleted shortly.