BUG: aero is disabled if you open 25 instances of Windows Photo Ga

  • Thread starter Thread starter Guest
  • Start date Start date
Dave said:
I opened 44 of my own files... Aero stayed active..


I got to 54...then an icon appeared in the notification area asking if I
wanted to disable Aero.
After clicking No, I got to 60...then Aero was turned off.
After closing the 60 photos, I re-enabled Aero...no restart required.
 
BillD said:
aero is disabled if you open 25 instances of Windows Photo Gallery
reproduction steps:

Not repro.

On my desktop machine, Aero shuts down at around 50 Photo Gallery windows.
This is a Nvidia 7900 with 512MB vidio RAM. After I close a few Photo
Gallery Windows, Aero springs back into action, no reboot is neccessary.
Also, I get a message from Windows telling me that Aero has been shut down
for performance reasons, because memory was running low. So it wasn't
totally unexpected for the user, that Aero went away.

The only "bug" here is that in your case, you do not seem to recover Aero
after you shut down the Photo Gallery Windows again. This is likely to be a
function of your video card driver, since the WDDM driver allocates and
frees the video memory. So the question would be, what video hardware and
driver are you using, and have you reported the issue to the video card
manufacturer? For example, via the Nvidia user forum, which is very active
and helpful.

As we discussed before - you need to distinguish between "surprising or
unusual behaviour" and "bug". Computers have been surprising users with
unusual results since Day One, and they continue to do so today. But only a
very tiny subset of these surprising behaviours is actually caused by a
*bug*, a software defect such as a programming error. Usually, they are just
a slight mismatch in the fidelity of representing user's expectations, in
software.

Your enthusiasm for locating bugs is commendable; but you need to refine
your concept of what constitutes a bug. Microsoft dev guy Roberto Farah has
compiled a great list of debugging and bug-hunting books and resources,
here:
http://blogs.msdn.com/debuggingtool...w-to-acquire-or-improve-debugging-skills.aspx
 
Andre Da Costa said:
Quote from Carey Frisch (MVP)
Your video card and Windows Vista are designed to share system RAM, but
only
when you need to do so. For instance, if you are running an application
(such as a graphics intensive game) that requires more memory than that
which
is available on your video card, the system kicks in to allow it to use
general computer RAM. However, when your graphics usage has no need for
system RAM, it's available for other uses. It's a very good technology.

This is actually inaccurate information that you have quoted, maybe being
confused with the behaviour of onboard graphics chipsets on laptops and
mini-ATX motherboards.

In Vista, system RAM is used for caching the windows, so that they can be
restored quicker. This is one of the reason that Vista seems to use lot
more memory than XP does, although the RAM is reallocated to applications
when they need it. This is irrelevant to the Aero issue being discussed
here.

ss.
 
Synapse Syndrome said:
This is actually inaccurate information that you have quoted, maybe being
confused with the behaviour of onboard graphics chipsets on laptops and
mini-ATX motherboards.
In Vista, system RAM is used for caching the windows, so that they can be

I respectfully disagree.

Actually, Vista's graphics memory design is new and somewhat more complex
than in previous versions, so it is easy to be off-target :-)

The WDDM uses a "virtual memory" model for graphics memory; with global
system memory providing the backing store for the graphics driver. So system
memory can indeed be used to mainpulate graphics data, even on machines
which have discrete graphics cards (ie no laptops with integrated graphics).

There's a short but thorough, readble description in this Microsoft paper:

Graphics Memory Reporting through WDDM
http://www.microsoft.com/whdc/device/display/graphicsmemory.mspx

So, a machine with more system memory will also have more graphics memory,
than a machine with exactly the same graphics card but less system memory.
 
Andrew McLaren said:
I respectfully disagree.

Actually, Vista's graphics memory design is new and somewhat more complex
than in previous versions, so it is easy to be off-target :-)

The WDDM uses a "virtual memory" model for graphics memory; with global
system memory providing the backing store for the graphics driver. So
system memory can indeed be used to mainpulate graphics data, even on
machines which have discrete graphics cards (ie no laptops with integrated
graphics).

There's a short but thorough, readble description in this Microsoft paper:

Graphics Memory Reporting through WDDM
http://www.microsoft.com/whdc/device/display/graphicsmemory.mspx

So, a machine with more system memory will also have more graphics memory,
than a machine with exactly the same graphics card but less system memory.

OK, I was going on what was discussed in the conversation a while ago,
"Shared memory with graphics card", which is still on the MS newsserver, but
strangely, not on Google Groups (I have noticed how that there is a lot
missing these days).

I know that you must be right, without reading your link right at the
moment. You should have got into that conversation to give the definitive
answer.

<bows>

ss.
 
Frank said:
I hate to give you the bad news (yeah right :-)) beetle brain, but that
behavior in Photo Gallery does not occur on any of our Vista Ultimate
installs...none of them.
I've dl'ed the op's URL file and tried it, only one image at a time opens
and only one instance of Photo Gallery opens.
I tried it using our own folders containing thousands of jpg images,
selected all of then and hit enter...only one instance of Photo Gallery
opens.
We cannot duplicate this behavior and if it is a bug as you say, then it
must be specific to certain installed configurations or Vista OS's.
I know you think you know everything, but obviously you don't.
Frank

When I tried it I got the behaviour that you described (i.e. one instance
and one image) if I unzipped the archive into its own "proper" directory
first. But I got the behaviour that the OP described (i.e many instances
and one image in each) if I tried to open the images while they were still
zipped into the archive. So I wouldn't necessarily dismiss the report out
of hand. What I didn't get though was Aero turning itself off, and I
couldn't be bothered to experiment to find out how many additional windows I
needed to open to make it do so.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top