Crash in qt_scale_image_32bit
-
Hi.
I got a crash report from user, for my Qt 4.8.4-based application (Win32).
It is an ACCESS VIOLATION in qt_scale_image_32bit<Blend_ARGB32_on_ARGB32_SourceAlpha>
The problem is that:
- I cannot reproduce the crash on my systems :-(
- Only that specific user can reproduce the crash and only on one of his systems (it's an old Laptop with no SSE support, running on Windows XP)
- It only happens with Release builds, the Debug build I provided didn't crash, he said
- Disabling the "visual styles" in compatibility settings did not make a change (still crashed)
- Running the app with 16-Bit color depth rather than 32-Bit doesn't trigger the crash
Detailed call stack:
@(e3c.3c0): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=ffffffff ebx=03e0236c ecx=ffffffff edx=ffffffff esi=02e74404 edi=00000000
eip=008f718b esp=0012ae40 ebp=0012aef0 iopl=0 nv up ei ng nz na pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010287
LameXP!qt_scale_image_32bit<Blend_ARGB32_on_ARGB32_SourceAlpha>+0x39b:
008f718b 8b3483 mov esi,dword ptr [ebx+eax*4] ds:0023:03e02368=????????
0:000> k
ChildEBP RetAddr
0012aef0 008f38c2 LameXP!qt_scale_image_32bit<Blend_ARGB32_on_ARGB32_SourceAlpha>+0x39b
0012af18 008ad69a LameXP!qt_scale_image_argb32_on_argb32+0x32
0012b150 008ac4dc LameXP!QRasterPaintEngine::drawImage+0x93a
0012b204 0071f88b LameXP!QRasterPaintEngine::drawPixmap+0x1dc
0012b314 005cbb33 LameXP!QPainter::drawPixmap+0x25b
0012b370 006cb5f0 LameXP!QPainter::drawPixmap+0x73
0012b4f0 006d82e7 LameXP!QConicalGradient::QConicalGradient+0x2340
0012ced0 00672ec8 LameXP!QPlastiqueStyle::drawControl+0x5877
0012cffc 005efc69 LameXP!QMenuBar::paintEvent+0x278
0012d0f4 00674222 LameXP!QWidget::event+0x619
0012d154 005ba39a LameXP!QMenuBar::event+0x252
0012d170 005b9c6f LameXP!QApplicationPrivate::notify_helper+0x9a
0012d430 0051e965 LameXP!QApplication::notify+0x136f
0012d470 005eb5c5 LameXP!QCoreApplication::notifyInternal+0x85
0012d550 005ebe1c LameXP!QWidgetPrivate::drawWidget+0x6e5
0012d5d8 005eb6f5 LameXP!QWidgetPrivate::paintSiblingsRecursive+0x36c
00000000 00000000 LameXP!QWidgetPrivate::drawWidget+0x815@Has anybody seen this before? Or have an idea what could cause this ???
Regards,
MuldeR -
Did you find anything in the "bug tracker":https://bugreports.qt-project.org/ ? If somebody has seen the issue before then it should be there.
-
Closest thing I found is:
https://bugreports.qt-project.org/browse/QTBUG-5493?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanelBut it's for v4.6.0, Closed and from 2009...
-
So, any more suggestions/ideas how I would go about this one?
I guess if I did open a bug report, I cannot provide a minimum example that reproduces the crash (as I cannot reproduce it myself at all), so it probably would be closed as "won't fix" right away...
Still the problem is very real, so what do I do next ???
-
+++ Update +++
I have created a very simple test application:
http://www.mediafire.com/file/xbm3bmgozyedg9r/QtTestApp.2013-03-03.7zThe source code is available here:
http://www.mediafire.com/file/lcr2hesh47y2f95/QtTestApp.2013-03-03.tar.bz2--
I sent this to the user and he could reproduce the crash !!!
Here is the stack trace:
http://pastie.org/private/iccugicw0bormqk0daqjhq--
I also asked the user to send me his system specs. They are here:
-
[quote author="MuldeR" date="1362435407"]+++ Update +++
I have created a very simple test application:
http://www.mediafire.com/file/xbm3bmgozyedg9r/QtTestApp.2013-03-03.7zThe source code is available here:
http://www.mediafire.com/file/lcr2hesh47y2f95/QtTestApp.2013-03-03.tar.bz2--
I sent this to the user and he could reproduce the crash !!!
Here is the stack trace:
http://pastie.org/private/iccugicw0bormqk0daqjhq--
I also asked the user to send me his system specs. They are here:
- http://i.imgur.com/xzuSyqo.jpg
- http://i.imgur.com/Aba1w5J.jpg
- http://i.imgur.com/rqTAJw6.jpg[/quote]
bump
Sorry, but really nobody knows what to do from here?
-
Okay, created an entry on the bug tracker in the hope somebody will notice it there:
https://bugreports.qt-project.org/browse/QTBUG-30121 -
It's been a while.
Back then, nobody really cared. But this recent fix might be related:
https://qt.gitorious.org/qt/eugenevotyakovs-qt/commit/343df131f7207d65932c6505769aa2fb7fc04713Haven't got around to try Qt 4.8.6, but I will give it a try soon...