Bug 307529 - It crash when I change the symmetry setting.
Summary: It crash when I change the symmetry setting.
Status: RESOLVED WORKSFORME
Alias: None
Product: ksudoku
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Ian Wadham
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-28 13:33 UTC by LO Kam Tao Leo
Modified: 2018-05-15 16:46 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 LO Kam Tao Leo 2012-09-28 13:33:43 UTC
When I try to change the symmetry setting, it hold a little bit, and the Crash Handler shows up and say it close unexpectedly. The crash handler given me the details is:Executable: ksudoku.EXE PID: 8652 Signal: EXCEPTION_ACCESS_VIOLATION (0xc0000005) 

Reproducible: Always

Steps to Reproduce:
1. Open the application
2. Click on the drop-down menu next to the label "Symmetry"
3. Select a option other than the default one
Actual Results:  
It closed unexpectedly

Expected Results:  
The symmetry setting should change and the program itself should keep running

-----Back trace-----
Application: KSudoku (ksudoku.EXE), signal: EXCEPTION_ACCESS_VIOLATION


ntdll.dll!ZwWaitForMultipleObjects() [[unknown] @ -1] at 0x779f013d
kernel32.dll!BaseThreadInitThunk() [[unknown] @ -1] at 0x7565339a
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ef2
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ec5


QtGui4.dll!QGraphicsItemPrivate::setVisibleHelper() [[unknown] @ -1] at 0x67d7c3fa
QtGui4.dll!QGraphicsItem::setVisible() [[unknown] @ -1] at 0x67d7ca51
ksudoku.EXE!QMap<QString,QString>::unite() [[unknown] @ -1] at 0x8d806e
ksudoku.EXE!QMap<QString,QString>::unite() [[unknown] @ -1] at 0x8d8bb7


ntdll.dll!ZwWaitForMultipleObjects() [[unknown] @ -1] at 0x779f013d
kernel32.dll!BaseThreadInitThunk() [[unknown] @ -1] at 0x7565339a
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ef2
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ec5


ntdll.dll!ZwWaitForWorkViaWorkerFactory() [[unknown] @ -1] at 0x779f1f26
kernel32.dll!BaseThreadInitThunk() [[unknown] @ -1] at 0x7565339a
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ef2
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ec5


ntdll.dll!NtRemoveIoCompletion() [[unknown] @ -1] at 0x779ef939
kernel32.dll!BaseThreadInitThunk() [[unknown] @ -1] at 0x7565339a
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ef2
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ec5
Comment 1 LO Kam Tao Leo 2012-09-28 13:44:04 UTC
I later try to change the difficulty setting and it happen with same result. The back trace as follow

Application: KSudoku (ksudoku.EXE), signal: EXCEPTION_ACCESS_VIOLATION


ntdll.dll!ZwWaitForWorkViaWorkerFactory() [[unknown] @ -1] at 0x779f1f26
kernel32.dll!BaseThreadInitThunk() [[unknown] @ -1] at 0x7565339a
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ef2
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ec5


ntdll.dll!ZwWaitForWorkViaWorkerFactory() [[unknown] @ -1] at 0x779f1f26
kernel32.dll!BaseThreadInitThunk() [[unknown] @ -1] at 0x7565339a
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ef2
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ec5


ntdll.dll!NtRemoveIoCompletion() [[unknown] @ -1] at 0x779ef939
kernel32.dll!BaseThreadInitThunk() [[unknown] @ -1] at 0x7565339a
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ef2
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ec5


ksudoku.EXE!QMap<QString,QString>::unite() [[unknown] @ -1] at 0xc58005
ksudoku.EXE!QMap<QString,QString>::unite() [[unknown] @ -1] at 0xc58bb7
ntdll.dll!RtlInitUnicodeString() [[unknown] @ -1] at 0x779fe38c
QtGui4.dll!QWidgetPrivate::sendPendingMoveAndResizeEvents() [[unknown] @ -1] at 0x679251a7
QtGui4.dll!QWidgetPrivate::sendPendingMoveAndResizeEvents() [[unknown] @ -1] at 0x679251a7
QtGui4.dll!QWidgetPrivate::sendPendingMoveAndResizeEvents() [[unknown] @ -1] at 0x679251a7
QtGui4.dll!QWidgetPrivate::prepareToRender() [[unknown] @ -1] at 0x67920939
QtGui4.dll!QWidget::render() [[unknown] @ -1] at 0x6792012b
oxygen.dll!qt_plugin_instance() [[unknown] @ -1] at 0x6881856d


ntdll.dll!ZwWaitForMultipleObjects() [[unknown] @ -1] at 0x779f013d
kernel32.dll!BaseThreadInitThunk() [[unknown] @ -1] at 0x7565339a
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ef2
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ec5


ntdll.dll!ZwDelayExecution() [[unknown] @ -1] at 0x779efd71
KERNELBASE.dll!Sleep() [[unknown] @ -1] at 0x75b33a8b
ole32.dll!CoGetTreatAsClass() [[unknown] @ -1] at 0x757dd98d
ole32.dll!CoGetTreatAsClass() [[unknown] @ -1] at 0x757dd87a
kernel32.dll!BaseThreadInitThunk() [[unknown] @ -1] at 0x7565339a
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ef2
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ec5


ntdll.dll!ZwWaitForMultipleObjects() [[unknown] @ -1] at 0x779f013d
kernel32.dll!BaseThreadInitThunk() [[unknown] @ -1] at 0x7565339a
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ef2
ntdll.dll!RtlInitializeExceptionChain() [[unknown] @ -1] at 0x77a09ec5
Comment 2 Ian Wadham 2012-10-01 04:16:52 UTC
I am sorry, I cannot help you with this one.  Clicking a combo box is a very basic operation which is mainly handled by library software and there are only a few lines of KSudoku code involved in this case.  KSudoku 1.1 is working fine on Apple OS X and Linux for all recent versions of KDE and Qt libraries.

Perhaps there has been a problem with installing the Windows versions of Qt, KDE and KDE Games or perhaps Windows does not like combo boxes in the status bar.  Do other KDE Games that have a difficulty combo box in the status bar work for you?  e.g. Bovo, Kapman, KNavalBattle, KBlocks, KBounce and more.

For more help, perhaps you could enquire on the KDE Windows mailing list 	kde-windows@kde.org
Comment 3 LO Kam Tao Leo 2012-10-02 02:34:22 UTC
It works on other games.And it only crash when change it BEFORE start the game, and its work if a game is in progress. Will it suggest that is a bug in the program in Windows version?
(In reply to comment #2)
> I am sorry, I cannot help you with this one.  Clicking a combo box is a very
> basic operation which is mainly handled by library software and there are
> only a few lines of KSudoku code involved in this case.  KSudoku 1.1 is
> working fine on Apple OS X and Linux for all recent versions of KDE and Qt
> libraries.
> 
> Perhaps there has been a problem with installing the Windows versions of Qt,
> KDE and KDE Games or perhaps Windows does not like combo boxes in the status
> bar.  Do other KDE Games that have a difficulty combo box in the status bar
> work for you?  e.g. Bovo, Kapman, KNavalBattle, KBlocks, KBounce and more.
> 
> For more help, perhaps you could enquire on the KDE Windows mailing list 
> kde-windows@kde.org
Comment 4 Gregor Mi 2018-05-15 16:46:39 UTC
Hello LO,
thanks for taking the time to do bug report. The years have passed and I will close this ticket. If you can still reproduce the bug with a more recent version, please feel free to open it again.