DoubleBuffer PageFaults?

A

abc

Hi,

I notice that my app (with a double buffer form) throws TONS of page faults
whenever it refreshes. I googled, and found the same complaint on GotDotNet.
Does anyone have any info on this, or could at least get this in the BUG
QUEUE!

Thanks,

Steve

Serious GDI+ bug on VS 2005 Posted on: 07/21/2005 07:41:23




Hi

Id be interested in hearing if anyone else can see this bug, it is
VERY easy to try and repro, really very easy.

Create a new basic windows app, C# will do.

In the forms constructor put this before or after the
InitializeComponent call:

this.SetStyle(ControlStyles.OptimizedDoubleBuffer,true);

build and run the app.

Use task manager to observe the processes PF delta.

Vertically enlarge the form.

It will be observed that the process generates many thousands of page
faults per second, with a full screen app at 1600 x 1200 I have seen in
excess of 50,000 PFs per second!

The problem is always present.

The problem also happens if we set DoubleBuffer property; although
this s described as Obsolete in the latest beta documentation.

The problem occurs with both 16-bit and 32-bit color settings.

It occurs at 1600x1200 and 1024x768

It occurs with desktop style set to Classic or Windows XP

It occurs when I use the NVidia driver for my GeForce FX 5200 or if I
boot XP in VGA mode (thus forcing it to use a different driver).

It occurts on both Win XP Professional (32-bit) and Windows XP
Proferssional 64 for AMD (The OEM version, NOT a beta)

I am using an Athlon 64 3400+, 1Gig and Asus K8V-SE DeLuxe
motherboard.

Basically the fault seems to be independent of driver, color depth,
resolution, refresh rate and operating system.

By not calling SetStyle for DoubleBuffer or OptimizeDoubleBuffer the
problem goes away, but the app then suffers from very bad flickering.

Setting both styles has no effect either.

This was first reported in bug: FDBK23039 but was then only seen in a
test version of a complex app that also uses some sophisticated class
libraries (under development) and some complex unmanaged (unsafe) library
(also under development) and naturally this was the main suspect, since it
access lots of memory and could have lay behind the page faulting.

Since the problem can very easily be reproduced with almost no effort,
it is now clear that it lies somewhere in the Framework, GDI+ or possibly
some component of XP (common to both 32-bit and 64-bit ?)

I have reported this to MS, althoung I cant disguise my intense
frustration at the apalling quality of their bug reporting system, after
entering this detailed report (that took me several hours to carefully test
and document) the stupid web based bug system refuses to accept > 2000
chars, forcing me to hastily edit and break it up and making almost
impossible to now follow.

Anyway I am very very curious to see if anyone else gets (or doesnt
get) this behavior.

H
 
L

Lloyd Dupont

If you could submit a simple sample reproducing the bug, THAT would be
usefull!!
Also it's limited on 2000chars BUT you could attach a document!
(basically your bug sample)
 

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

Top