SEAMONKEY 2.49.1 MOVIE

Multiprocess enabled (forced, I suppose you might say?) 2/2 Perhaps an extension is contributing to the issue?ĭid the OP ever figure out what was going on here, cause it just hit me too! So FF, even FF 58, is still affecting 'things', things external to FF.

Likewise with others I had just attempted to play that had just failed now played as expected.

Then went I clicked on the video clip that was failing on me - in my video player, totally external to any browser, which opened right up & played, as expected. I manually refreshed those few pages, which then did load as expected. maybe they run through some cloud 'proxy' type of thing, that say something like 'inaccessible at present' with a prompt to refresh. I also refreshed a few pages that I saw failed to load, properly. It is then when I realize that the last FF 'window' was not a window, but was a queued up set of XSS warnings - which I gleefully dismissed without looking at - at all. So thinking its some fart in FF, & I'm going to be left with shutting it down & restarting it. CPU is 'OK', but I'm seeing what I expect is unexpected I/O, on the main FF process, & its immediate child. So I try another player, & again more odd error messages &/or playback failures.Īnd I check RAM & CPU, & I've only got 1 browser open (FF, where I usually have more), & otherwise nothing special going on. But then I'm getting the same on various clips.Īnd I think, oh, I hope my drive isn't going bad. Somewhere along the line, one again, external video player was failing.įirst thought was it was a corrupted clip. (Usually I get multiple XSS warnings on startup, which I simply dismiss, consecutively.)Īnd FF seemed to load faster (actually settle down faster, as in initial higher CPU load dropped down to more 'regular' CPU load, faster). This time when I started up, there seem to only be one XSS warning, which I dismissed. I'll just state that there were numerous (a dozen or so is numerous enough for) queued up XSS warnings - which I hadn't realized, which I do not think came up on browser startup (from Session Restore) - which I've come to expect. Now, WITHOUT ANY EVIDENCE (much less any clue as to what I'm talking about). I will say this issue completely subsided with 'Quantum' (FF 57+). So, with FF 56 (圆4 as it is, can't really say about other versions or bitness), on my system, it seems to eat RAM FAR quicker & to a much greater degree, then I'm seeing once I've turned hardware acceleration off.

SEAMONKEY 2.49.1 MOVIE

Īnyhow, during this time, other then slowness in FF 56 (probably understandable, well, not actually), I've not run into any irregularities outside of FF (like with my movie players). I'd close some (many) extraneous tabs (40 windows, 937 tabs, at present), to see how/if RAM drops, but I'm somewhat hampered by, Taskbar Icons are Reordered when open from Session Restore, so at some point I'll just Quit, then reopen from Session Restore.Īlso, I have & have had SeaMonkey open, using ~1.5 GB RAM.Īnd I (accidentally) opened an other (rather huge too) FF Profile, FF 54, perhaps it was, 32-bit - without NoScript installed, & that (eventually, 17 min, I think it was) crashed, OOM. (It is time for a restart, but I want to thrash it some more.) At ~3 GB, FF was running fine.Ĭurrently I'm noticing some slight slowness. I don't think I'm seeing anything in (Windows) Event Viewer.Īnd in that respect, what I've done so far is to disable Hardware Acceleration ( true), restarted, & with that, I've been running a few days now (including sleep cycles), & ATM FF is (only) using 3.9 GB (having only hit that, from ~3 GB, over the last 24 hours). Note that with FF, while I am specifically, though not necessarily wantonly, 'pushing' FF more so then what I am (currently) with SeaMonkey. I close FF (I have not seen the issue with SeaMonkey) & what didn't work a moment ago, now works as expected.

At this time MPC / MPC-BE also spit out error messages (different, I'll have to update.) & may or may not play a particular media file. Combination of Legacy & hybrid & webex.Īnyhow, out of the blue, recently (& where I've noticed the issue), I'll click on a media file (movie clip), & my media player, MPlayer (using the MPUI GUI) spits out, 'not enough storage space is available to process the command'. From a window or two, to now where I've got many (count will have to wait).Įxtensions are minimal. My (Session Restore) has grown - quickly. With FF, in relatively short order, I can eat RAM. Intel i5-3570, on-CPU video, HD 4000 graphics Not enough server storage to process command - Revisit Not enough server storage to process command? Not Enough Storage Space Is Available To Process The Command

Seamonkey 2.49.1