Bug 259006 - kGameRenderer crash when doing QT_FATAL_WARNINGS=1 kmines
Summary: kGameRenderer crash when doing QT_FATAL_WARNINGS=1 kmines
Status: CONFIRMED
Alias: None
Product: libkdegames
Classification: Frameworks and Libraries
Component: kgamerenderer (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Dmitry Suzdalev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-06 13:52 UTC by Jaime Torres
Modified: 2022-11-07 15:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaime Torres 2010-12-06 13:52:59 UTC
Application: kmines (3.0 (02 Aug 2007))
KDE Platform Version: 4.5.85 (4.6 Beta2) (Compiled from sources)
Qt Version: 4.7.2
Operating System: Linux 2.6.36optimum x86_64
Distribution (Platform): openSUSE RPMs

-- Information about the crash:
- What I was doing when the application crashed:

QT_FATAL_WARNINGS=1 kmines

- Custom settings of the application:

Stdout:
QPainter::begin: Paint device returned engine == 0, type: 2

The crash can be reproduced every time.

-- Backtrace:
Application: KMines (kmines), signal: Aborted
[KCrash Handler]
#6  0x00007f1409615965 in raise () from /lib64/libc.so.6
#7  0x00007f1409616e66 in abort () from /lib64/libc.so.6
#8  0x00007f140a3572c7 in qt_message_output (msgType=<value optimized out>, buf=<value optimized out>) at /g/kde4svn/qt/src/corelib/global/qglobal.cpp:2282
#9  0x00007f140a35745d in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtWarningMsg, msg=
    0x7f140b76cf38 "QPainter::begin: Paint device returned engine == 0, type: %d", ap=0x7fffa23e3150) at /g/kde4svn/qt/src/corelib/global/qglobal.cpp:2328
#10 0x00007f140a357c65 in qWarning (msg=<value optimized out>) at /g/kde4svn/qt/src/corelib/global/qglobal.cpp:2410
#11 0x00007f140b2260f1 in QPainter::begin (this=0x1780f78, pd=0x7fffa23e3450) at /g/kde4svn/qt/src/gui/painting/qpainter.cpp:1773
#12 0x00007f140b226310 in QPainter::QPainter (this=0x1780f78, pd=0x7fffa23e3450) at /g/kde4svn/qt/src/gui/painting/qpainter.cpp:1491
#13 0x00007f140cd787bb in KGRInternal::Worker::run (this=0x1ca22a0) at /g/kde4svn/kdegames/libkdegames/kgamerenderer.cpp:548
#14 0x00007f140cd79296 in KGameRendererPrivate::requestPixmap (this=0x1cd8000, spec=..., client=0x0, synchronousResult=0x7fffa23e3810) at /g/kde4svn/kdegames/libkdegames/kgamerenderer.cpp:481
#15 0x00007f140cd79457 in KGameRenderer::spritePixmap (this=0x1cd6550, key=..., size=<value optimized out>, frame=-1, customColors=...) at /g/kde4svn/kdegames/libkdegames/kgamerenderer.cpp:396
#16 0x0000000000416a8b in KMinesScene::KMinesScene (this=0x1cd6540, parent=<value optimized out>) at /g/kde4svn/kdegames/kmines/scene.cpp:66
#17 0x000000000040d83f in KMinesMainWindow::KMinesMainWindow (this=0x17ec7e0, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /g/kde4svn/kdegames/kmines/mainwindow.cpp:87
#18 0x00000000004172b8 in main (argc=1, argv=0x7fffa23e3d88) at /g/kde4svn/kdegames/kmines/main.cpp:56

Reported using DrKonqi
Comment 1 Stefan Majewsky 2010-12-07 23:20:37 UTC
Seen that before, most likely some problem with KGameRenderer's multithreaded rendering pipeline.
Comment 2 Justin Zobel 2020-12-04 05:03:23 UTC
Thank you for the report, Jaime.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 3 Jaime Torres 2020-12-06 08:30:29 UTC
I had a patch that fixed this warning/error.
It is available in https://phabricator.kde.org/D9198

Unfortunately, it can be reproduced just launching QT_FATAL_WARNINGS=1 kmines
Comment 4 Justin Zobel 2022-11-06 23:48:18 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Jaime Torres 2022-11-07 15:48:35 UTC
Yes, the lack of initialization still affects this game, but only when the QT Warnings become errors.