This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I was assigned to review a crash that affect a few users sporadically. Program is written in C++ (no clr). The call stack of the crash is:
GdiPlus!ValidateBitmapInfo
GdiPlus!CopyOnWriteBitmap::CopyOnWriteBitmap
GdiPlus!CopyOnWriteBitmap::Create
GdiPlus!GpBitmap::GpBitmap
GdiPlus!GdipCreateBitmapFromGdiDib
MyApp!Gdiplus::Bitmap::{ctor}
The crash seems to be random, environmental, and complex (impossible) to reproduce user steps.
Could this crash be caused by memory fault?
I can see some debug data from the DUMP file. BitmapInfoHeader seems to be correct:
{
biSize=40
biWidth=1224
biHeight=1584
biPlanes=1
biBitCount=8
biCompression=0
biSizeImage=1938816
biXPelsPerMeter=5669
biYPelsPerMeter=5669
biClrUsed=0
biClrImportant=0
}
Pointer with data was copied and allocated in a std::vector prior to building the GdiPlus::Bitmap.
This is what comes from Visual Studio opening the miniDump file:
Unhandled exception at 0x73EF12D3 (GdiPlus.dll) in file.dmp: 0xC0000005: Access violation reading location 0x06101002.
Please, any help is welcome!
Best regards
Márcio
What users say?
They are performing a conversion where I take an image when suddenly it crashes... they run again and the error does not happen again.
One user reported he was having the issue always when converting a batch of files. I downloaded his files and performed the conversion without the error...
What is the crash - read/write access violation, or something else?
Have you tried to reproduce it with a debug build of your application with the debug run-time checking enabled?
Hi, @David Lowndes
The crash is access violation
I have updated the question.
Running a debug build or a release with symbols and checks turned on would help me if I could reproduce the error, or am I wrong?
I am not sure, but this approach may not help me to detect the root cause, considering the access violation happens inside Gdiplus.dll. It there a GdiPlus.dll built for debug?
I really appreciate you support. Thank you, I hope you can bring some other ideas.
A debug build with the run-time checks on may identify a problem that may only occur randomly in a release build, so if you've not done it, give it a go.
I am not following at all... The issue seems to be happening inside gdiplus.dll. Turning on debug checks will not change gdiplus.dll to make it start asserting for inconsistencies. When building in debug, VS links to MFC and stdlib debug versions, and that would only help me for the case the issue was affecting those libraries. I searched for a debug version of gdiplus.lib but haven't found anything.
Unless other people's applications are experiencing the same problem, the problem presumably originates (even if it doesn't happen directly) in your code - hence why trying the run-time debug options may identify something.
Also check out the static code analysis option.
Is your problem solved? Can you provide a minimal reproducible example?
Sorry, I missed that!
I decided to post the issue to MS developer community:
Several months has gone, it is likely the issue will not get attention so soon.