| Summary: | kpat crashes when grandfather is selected | ||
|---|---|---|---|
| Product: | [Applications] kpat | Reporter: | Uli <uliwehner> |
| Component: | general | Assignee: | Stephan Kulow <coolo> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | 0inkane, aacid, justin.zobel, kde-games-bugs-null, shlomif |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 3.6 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Uli
2018-11-24 17:02:45 UTC
Shlomi, Fabian more crashes in the solver/memory allocator stuff Can you please have a look? We did not have crashes, we got your changes in and now we do I'll take another look at it this weekend at the latest, though my issue is that I couldn't reproduce any crash so far locally. I'll try running the program under sanitizers and valgrind again, maybe that catches an error. (In reply to Fabian from comment #2) > I'll take another look at it this weekend at the latest, though my issue is > that I couldn't reproduce any crash so far locally. I'll try running the > program under sanitizers and valgrind again, maybe that catches an error. kpat master seems to work perfectly fine here as well (mageia v7 x86-64) when selecting grandfather clock. No crashes so far (In reply to Shlomi Fish from comment #3) > (In reply to Fabian from comment #2) > > I'll take another look at it this weekend at the latest, though my issue is > > that I couldn't reproduce any crash so far locally. I'll try running the > > program under sanitizers and valgrind again, maybe that catches an error. > > kpat master seems to work perfectly fine here as well (mageia v7 x86-64) > when selecting grandfather clock. No crashes so far oh sorry - checked with grandfather (not clock) too now and it seems fine too. note for reproducing issue: i have this happen on 2 separate laptops, both OpenSuse Tumbleweed, been going on for a couple of weeks. open kpat, select a game other than grandfather. I usually play Simple Simon or FreeCell. Play it. Then select new game, select grandfather. application will crash every time on both PCs. If you open again, select grandfather as the first game, it works fine. Let me know if you need any additional details Uli Do you start the new game before or after completing the old one? And if you start it before the game is complete, is the solver in a certain state (still solvable, unsolvable, unknown)? Fabian, interesting. I usually complete the game, then choose a different one. However, i just tested just starting kpat, starting simple simon, play a little, then switeh to grandfather without completing the game. Grandfather did not crash kpat that time. I do believe the crashes are solver related since since solver gets stuck at times for extended periods of time. Thank you for the crash report. 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. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! (In reply to Bug Janitor Service from comment #9) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! |