Sorry. I should have also mentioned that I'm running Mozilla under Warp4+FP12.
Ralph Cohen wrote: > I've run into some very strange behavior with v1.1. Whenever I close > the last Mozilla window started under a -turbo process, the window > closes but the Mozilla -turbo process spawns another process. The > original process then closes but for about the next 30 seconds the new > one eats up about 50%-60% of the CPU (PIII 450) cycles and there's a > lot of disk activity. Not surprisingly, while that's going I can't > start any new sessions. Like I said, very strange. > > Version 1.0, however, runs on the same system without any of this > strangeness. When I close the last Mozilla window, it closes with > just a tiny spike in the CPU cycles and I can open a new window > immediately. Also, no new processes are spawned. I also downloaded a > new copy of 1.1 and installed it in a new directory without migrating > any profiles but the result was still the same. Closing a Mozilla > window not opened under a -turbo process, however, causes no problems. > > Another strange thing under v1.1 is that the first time I open a > Mozilla window - either by itself or under a -turbo process - it opens > at the bottom of the screen with only the title and menu bars showing. > Subsequent Mozilla windows open next to where ever I move the first > window, but the first one is always at the bottom. Once again, I > don't have that problem with V1.0 or earlier betas. I'm using the > Matrox video drivers 2.54.130. This sounds like the problem Will > Honea and others have reported. > > Any comments, suggestions or magic spells? Can anyone else replicate > this? > > Thanks, > > Ralph Cohen >
