Skip to content

Crash when joining Arena, QUnhandledException #132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Mistra opened this issue Sep 11, 2021 · 6 comments
Open

Crash when joining Arena, QUnhandledException #132

Mistra opened this issue Sep 11, 2021 · 6 comments

Comments

@Mistra
Copy link

Mistra commented Sep 11, 2021

I'm using version 10.0, AppImage
I'm opening an arena at hero selection panel when the Tracker crashes. The installation is fresh, brand new.

Here are some logs

11:33:58 - GameWatcher(3): New arena: choosing heroe.
11:33:58 - DraftHandler: Begin hero draft.
11:33:58 - GameWatcher(4): Found SetDraftMode - DRAFTING.
11:33:58 - DraftHandler: No continue draft because already drafting or no hero.

11:33:58 - GameWatcher(29): LoadingScreen: GAME_MODE -> DRAFT
11:33:58 - GameWatcher(29): Entering ARENA (loadingScreenState = arena).
11:33:58 - DeckHandler: Enter arena
11:33:59 - DraftHandler: Hearthstone arena screen NOT loaded from settings.
OpenCV Error: Unsupported format or combination of formats (type=0
) in buildIndex_, file /home/triodo/opencv-2.4.13.5/modules/flann/src/miniflann.cpp, line 315
terminate called after throwing an instance of 'QUnhandledException'
  what():  std::exception
fish: Job 1, './ArenaTracker.Linux.AppImage' terminated by signal SIGABRT (Abort)

Let me know if there are any other infos I can give, in case you want to dive in.

@supertriodo
Copy link
Owner

cant help, sorry

@Mistra
Copy link
Author

Mistra commented Sep 11, 2021

Uhmmm, meanwhile I was trying to download the source and debug it myself but this comment isn't encouraging.
May I know why, out of the blue, you are basically suggesting there's nothing to do?

@supertriodo
Copy link
Owner

I'll help, it's just I cant reproduce it myself.

@Mistra
Copy link
Author

Mistra commented Sep 11, 2021

Ok, if you are still in.

I managed to understand something is happening when you call line 1974 @ DraftHandler.cpp
ScreenDetection screenDetection = futureFindScreenRects.result();

The debugger stops at d.waitForResult(0); of QFuture

I understand there's something that... breaks the promise/future? Sorry It's been years I don't touch C++, let alone QTish C++

Does it ring any bell there? This afternoon I'll keep diving in, it's fun!

@Mistra
Copy link
Author

Mistra commented Sep 11, 2021

It turns out, that call somehow asks the w-server something (coordinates?). To draw the big dots with the card score if I understand right.
The issue here seems to be QT related, I use Wayland on GNOME. Infact when I switched back to X everything works fine. I'll see if I can manage to catch that unhandled exception or understand more why with Wayland the framework doesn't work.

@supertriodo
Copy link
Owner

I see, I haven't yet tested AT on wayland.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants