- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
This is an Old Comment !
It's time to upgrade.
Admin
Admin
Why is running out of system resources a WTF?
Captcha = Immitto = Something that only happens once in a while.
Admin
Radio announcer: (shuffling papers) I have here in my hands a magnificent picture of this really hot chick holding our sponsor's product, and let me tell you, if you could see her you'd want to rush right out and getcha somma this stuff.
Radio is the "theater of the mind". So if your audience even imagines our marketing image, you're going to need a Super License. Call or email your Account Executive now! You don't want the hot chick to leave, do you?
Admin
Admin
(If it is running out of memory instead of disk space, it should try this trick they invented back in oh about 1965 or so: swap something to disk.)
Admin
Note to self: Don't use advertising agencies that think radio is a visual media... It only ends in tears (or appearing on DailyWTF).
Admin
No. It's not allowed. In fact, to save time, I think the system should automatically enter 3 posts to every new article:
Admin
Admin
The Real WTF probably is requiring 65 GB before the setup even bothers to try installation.
Admin
01001110 01101111
Admin
If only that dialog box did represent what automatic changes Excel made to text as you type....
Admin
We have a winner.
Admin
Obviously, we've been meta-trolled by "Captain Obvious"
Admin
Admin
Admin
Wow - lower case and all!
Admin
It's just that it couldn't do proper math anymore, that's why 65 GB suddenly were less than 65 GB. Just like it's going to take 606MB / 16.3MB/s = 35minutes to copy my files. [image]
Admin
Why? What's the big deal?
Admin
You mean in ears?
Admin
Wow - lower case and all!
[erm. sorry. forgot the quote.]
Admin
Pardon me? I though this automation has been implemented months ago...
Admin
Pardon me? I thought this automation has been implemented here months ago.
Admin
Admin
That's exactly what I thought when I bought my first 1 GB disk 10 or 15 years ago. Nowadays I'm 64 GB short....
Admin
TB? There is a shot for that....
Admin
I read the Daily WTF for the captcha jokes. Please keep them coming.
captcha: Iamanidiot
Admin
Don't forget the ob captcha joke -- this can just be randomly attached to one of the first three comments.
Captcha: Appellatio Sex in the mountains?
Admin
Oh, and there's no way to tell you're running low until suddenly hot damn fook me I'm outta handles?
Admin
Admin
Admin
Nah, I think we should display a big message saying "Warning: Windows is low on handles!"
Then we can all laugh at the clueless (l)users who call the helpdesk and say "I cut all the handles off my luggage and put them in my floppy drive, what's wrong with my computer?"
Admin
I'm going to guess the denied installation is a roundoff problem--the drive having a tiny bit less space than the installer demands.
Admin
Back in the days of Windows 3.0, there was a memory limit of 64K. And it wasn't per application, oh noes!, it was the entire system. If your application used too many windows, fonts, bitmaps, icons and so on, then the entire system showed the problem, being unable to create any more.
I think Windows 95 doubled this pool size to 128K. I don't know what limits may be in force under, say, XP.
You got it. Welcome to Windows: you'll never look back now.Admin
As always it is more complex than that... Win 3.x had a number of heaps (3 IIRC) at 64K each. Window handles were a sort of index into one of these, pointing at a data structure that could in extreme cases be several hundred bytes long. Win9x added two more, and allowed these to be up to 2MB. A bunch of stuff was moved into the two big ones, which reduced the pressure on the small ones. No, I don't remember what went where.
The NT-based Windowses (NT, 2K, XP, Vista) didn't do this, although I have heard rumours of a 16384-handle limit on the number of some kinds of resource.
Admin
Admin
Admin
Since hard drive manufacturers mislabel their products, the 65 GB hard drive probably only has 58 GB, so the error is correct.
Admin
If that were the case, TRWTF would be the software using the term GB when it means GiB.
Admin
The Old Coot dialog is old; I recognize what library they're using and (approximately) what version of it too. Time for them to upgrade, especially on Macs or Windows...
Admin
Thank you.
Admin
Famous last words...
Admin
This is an old complaint.
It's time to upgrade!
Admin
To clear all misunderstanding:
The maximum number of window handles per desktop (see CreateDesktop()) is about 32K. There is also an arbitrary limit of number of handles per process which is 10000 by default, but can be changed by a registry setting.
There is limit on number of GDI handles, which depends on session heap usage (separate per terminal session).
There is no explicit limit on number of file handles or other kernel handles (synchronization objects, etc), other than non-paged pool exaustion. Pre-Vista/2008, NP pool size was limited at 256 MB for x86 flavor. There is no explicit NP pool size limit now, other than physical memory size (1/4 of it) and 2GB of kernel space in x86 OS.
Admin
Admin
Picture = 1000 words
x = words per minute
1000/x = cost per minute for 1 picture
Admin
...wait... did I just learned something on TDWTF?
Admin
He said "system resources". What it is running out of are, unsurprisingly, system resources. (More formally, GDI and USER objects) Specifically, Windows has a limited number of slots for data structures of things to be drawn on the screen.
When this is exceeded, there's no more room to even show an error message.
@RBoy, I think the question is how is it not a WTF.
Admin
There has to be some limit - you can't do runaway dynamic allocation for this, since when it eventually does run out of kernel address space it'll crash the kernel. The limit is configurable in the registry.
Microsoft thought it would no longer be a problem in the 32-bit OS (because, see, the limit is so much bigger than the 16K it used to be, so now it should be enough for anyone), so they didn't include a function to check it in the win32 API, and they broke win16 API function that checks it.
Admin
Not knowing much about the guts of Windows, my first guess would be that the window handles consume numbers, though some of the explanations above would seem to indicate that I'm wrong. The reasoning for my initial guess is that to me the problem looks similar to what happens on Unix-like systems with processes. Process identifiers are N-bit integers (on my Linux box, it looks like N=16, though there's probably no theoretical reason that you couldn't have N=32 or N=64), and when you run out of available numbers, you can't even start a root shell to kill any processes.
Yes, I accidentally wrote a fork bomb while working on an assignment for my operating systems class in college. Yes, I did have to press the reset button on the case of my Linux box.