Not Enough Storage Space Is Available To Process The Command
IRP Stack Size.
Been there done that.
Not enough server storage to process command?
Not enough server storage to process command - Revisit
No more IRP stack locations?
But that was over a DECADE ago.
Of late, I've been hitting it again...?
Intel i5-3570, on-CPU video, HD 4000 graphics
SeaMonkey 2.49.1 x64
Firefox 56 x64
NoScript current #dev
Just the other day, put in MS .NET 4.7.
Other then that... nothing really.
I've been messing with FF a bit. Certainly more then I have in the past.
With FF, in relatively short order, I can eat RAM.
Good chunks of RAM. 5, 6, 7, 8 GB of RAM.
- Is that "right", does that make sense?
In some respects no, but possibly?
My (Session Restore) has grown - quickly. From a window or two, to now where I've got many (count will have to wait).
Extensions are minimal. Combination of Legacy & hybrid & webex.
Anyhow, 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". MPUI hangs, I have to kill it. 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.
I close FF (I have not seen the issue with SeaMonkey) & what didn't work a moment ago, now works as expected.
Note that with FF, while I am specifically , though not necessarily wantonly, "pushing" FF more so then what I am (currently) with SeaMonkey.
I don't think I'm seeing anything in (Windows) Event Viewer.
Is this a new "feature" of FF?