New
#11
Windows 7 Bug?
-
-
New #12
However, in this case, it's not the system running out of typical resources. Once I had 75 Explorer Windows opened, I checked my CPU, memory and everything else and my box was more or less idle with less than 35% of the ram consumed. I opened up 5 more and it just hung.It may be possibly unfortunate that windows does not do a better job of protecting itself from running out of resources but yes that's the way it is. Open 80 instances of ANYTHING and you will probably drag windows down to a crawl or even a full stallout as everything is fighting for the last remaning byte of ram or window handle.
When attempting to close the open windows, the box hung. When I checked task manager I only had 1 explorer.exe running consuming about 70MB of RAM. I ended process on that process and now my box is just sitting there with the desktop background with no icons, no start menu, nothing else. Hard drive is doing nothing. Box is totally hung.
So, while nothing most people would ever see in a million years...still interesting and could probably be handled a bit more gracefully.
-
New #13
Perhaps you have reached the limited number of processes across the OS, not just Explorer.
Who knows, maybe the legacy code is still there that limits it despite having 24GB of RAM and 6-Core processors.
-
New #14
agreed, it could be handled in a much better way, rather than crapping out and causing the whole system to be unstable.However, in this case, it's not the system running out of typical resources. Once I had 75 Explorer Windows opened, I checked my CPU, memory and everything else and my box was more or less idle with less than 35% of the ram consumed. I opened up 5 more and it just hung.It may be possibly unfortunate that windows does not do a better job of protecting itself from running out of resources but yes that's the way it is. Open 80 instances of ANYTHING and you will probably drag windows down to a crawl or even a full stallout as everything is fighting for the last remaning byte of ram or window handle.
When attempting to close the open windows, the box hung. When I checked task manager I only had 1 explorer.exe running consuming about 70MB of RAM. I ended process on that process and now my box is just sitting there with the desktop background with no icons, no start menu, nothing else. Hard drive is doing nothing. Box is totally hung.
So, while nothing most people would ever see in a million years...still interesting and could probably be handled a bit more gracefully.
I still think it's a bug and NOT a feature. Also, whilst 75 explorer windows sounds like a lot, in the days of ssds, 24gb mem, 6 core processors, why shouldnt the OS handle it? Answers on a postcard....
-
New #15
-
New #16
No, it's not a resource issue. The Explorer.exe process climbs to around 200MB at around 75 open windows... The system is still lightening fast but as soon as you hit the 76th Window, BANG the desktop corrupts, explorer crashes and you're led to believe that your i7 is now a 486 in disguise... Call that a feature? Thought not.
-
New #17
-
New #18
I still don't see why this deserves an entire debate. Most people don't need 75-80 explorer Windows open.
-
New #19
I found more bugs in Windows 7. When I run programs simultaneously from several external USB HD's and then constatly plug and unplug all USB cables, some programs stop running.
Another bug I found, using my test machine, is that when I cut the power from the main switch when Windows is booting, after 20 or 30 retries Windows can no longer read my HD.
All these bugs, why can't they give us a working OS?
-
Quote