Jump to content

Client Crashes Repeatedly When Selecting Betsize Field


Insideman
  • Priority: Medium Status: On backlog

Yesterday, Thursday the 20th of June, my client crashed twice during a two hour session of 4 tables of Banzai, when I attempted to manually enter a betsize into the betsize field. Fortunately, I was recording my session and was able to see precisely what happened. This could be a coincidence, but both times I was on the button. When the action came to me I selected the betsize field and as I was entering a betsize, the client crashed. The button positioning could be relevant, because if it happened every single time I entered a betsize, that would be very obvious. My sense is that this bug seems to come and go with different client versions (or maybe it only happens with very specific sequences and is therefore normally rare), but it happened twice in nearly the same way yesterday in a single session.

I am using a dedicated number pad from the brand Qisan. The model is Magicforce | smart '21-Key Mechanical Numeric Keypad'.

Incident occured at 20:45 (Hand #2110298122) and 20:58 BST (Hand #2110307079).


User Feedback

Recommended Comments

I've uploaded the file as per your instructions. The timestamps for the video file are 1:40 and 1:53.

I also played another 90 minute Banzai session today without clicking into the betsize field and there were no crashes.

Link to comment
Share on other sites

Was suspecting a stuck button (stuck in onpressdown, logically, not physically stuck) could cause it, cause my wireless logitech keyboard gets that from time to time, having a button stuck until I press it again. This might not be @Insidemans case tho. And I've managed to replicate the crash 100% of the time by just having a letter pressed while selecting and deselecting the bet amount. Works with numbers too not just letters,  works on any game mode, cashgame, banzai, hexa. Does not crash in popup buyin textboxes! You have to be in BB mode, if you're in chips mode then it does not crash in any game mode. Might be worth seeing if it still crashes for you if you set it to chips @Insideman to see if it's related.

These are the crash messages, only seen the last one with this bug:

ExecuteRelaxCEFEngineAsChildProcess - CefExecuteProcess exited with 0

<process started at 15:40:29.082 has terminated with 0xc0000409 (EXCEPTION_STACK_BUFFER_OVERRUN)>

 

The "[CEditBoxStub::InputChar] check failed by mask" might play a part, but just spamming this error is not sufficient, it requires selecting the bet number, also this error happens in buyin textboxes too where it does not crash. Also, this error happened even when typing just numbers which should not fail right before the crash, possibly due to the action of selecting, skipping the input check and passing the unsafe input directly to a variable or the method dealing with bb to chips conversion 🤷‍♂️

 

Edited by FeelsBadMan
  • Like 2
Link to comment
Share on other sites

12 hours ago, Stubbe-Unibet said:

Thanks!
Has it been smooth sailing since the original report, or have you had further crashes?

I don't usually play Banzai, I was just doing the black belt mission to collect the Germany team. I haven't noticed it in other formats that I've played since then. I think my usage of the betting field also varies depending on the format. I can throw in another session of Banzai tomorrow. Feelsbadman seems to have some interesting thoughts on what might be causing the issue. I generally play with BB stacks on to reduce mental processing overhead. That makes me think that there is some translation layer involved when doing that, that might be triggering the crashes as well (Feelsbadman also implied ths). I will leave it on for now, for when I play Banzai tomorrow and try not to avoid the betsize field.

7 hours ago, FeelsBadMan said:

Was suspecting a stuck button (stuck in onpressdown, logically, not physically stuck) could cause it, cause my wireless logitech keyboard gets that from time to time, having a button stuck until I press it again. This might not be @Insidemans case tho. And I've managed to replicate the crash 100% of the time by just having a letter pressed while selecting and deselecting the bet amount. Works with numbers too not just letters,  works on any game mode, cashgame, banzai, hexa. Does not crash in popup buyin textboxes! You have to be in BB mode, if you're in chips mode then it does not crash in any game mode. Might be worth seeing if it still crashes for you if you set it to chips @Insideman to see if it's related.

These are the crash messages, only seen the last one with this bug:

ExecuteRelaxCEFEngineAsChildProcess - CefExecuteProcess exited with 0

<process started at 15:40:29.082 has terminated with 0xc0000409 (EXCEPTION_STACK_BUFFER_OVERRUN)>

 

The "[CEditBoxStub::InputChar] check failed by mask" might play a part, but just spamming this error is not sufficient, it requires selecting the bet number, also this error happens in buyin textboxes too where it does not crash. Also, this error happened even when typing just numbers which should not fail right before the crash, possibly due to the action of selecting, skipping the input check and passing the unsafe input directly to a variable or the method dealing with bb to chips conversion 🤷‍♂️

 

 

Thanks for the input. It doesn't sound like BB mode is the culprit here.

Link to comment
Share on other sites

19 hours ago, Insideman said:

I don't usually play Banzai, I was just doing the black belt mission to collect the Germany team. I haven't noticed it in other formats that I've played since then. I think my usage of the betting field also varies depending on the format. I can throw in another session of Banzai tomorrow. Feelsbadman seems to have some interesting thoughts on what might be causing the issue. I generally play with BB stacks on to reduce mental processing overhead. That makes me think that there is some translation layer involved when doing that, that might be triggering the crashes as well (Feelsbadman also implied ths). I will leave it on for now, for when I play Banzai tomorrow and try not to avoid the betsize field.

Thanks for the input. It doesn't sound like BB mode is the culprit here.

So, my update today after playing approximately 45 minutes of Banzai with the special Windows client is that I wasn't able to reproduce crashes by using Feelsbadman's methodology (assuming I did it correctly). I tried pressing a key on my number pad before selecting the betsize field. This didn't work, it just spammed the number and didn't crash. I tried the same with my keyboard (HyperX Alloy Origins 60) using a letter. This didn't spam a letter (as I imagine is normal) and it also didn't crash whilst selecting and deselecting the bet size. All in all I made an effort to use my number pad, but was unable to provoke any crashes. All of this was done in BB mode.

I should add that what I think I typically do (and when the crashes happened) when selecting the bet size is to double-click and not select by moving the mouse cursor. I've tried to do this deliberately, but the client also doesn't crash. For me at least, there doesn't seem to be a clear trigger that is 100% reproducible.

Link to comment
Share on other sites

Another example of crashing the client with the textbox, same as above. I have the number 2 pressed and I'm just clicking the bet input field to select it. This doesn't necessarily mean that spamming is a necessity to crash, it might happen without as well, it's just easier to replicate. BTW this is one game, edited out the login downtime, but didn't edit out any of the text box fiddling, this is all I did to get it to crash 4 times. And this crash does not generate a dmp. 

  • Like 1
Link to comment
Share on other sites

6 hours ago, FeelsBadMan said:

Another example of crashing the client with the textbox, same as above. I have the number 2 pressed and I'm just clicking the bet input field to select it. This doesn't necessarily mean that spamming is a necessity to crash, it might happen without as well, it's just easier to replicate. BTW this is one game, edited out the login downtime, but didn't edit out any of the text box fiddling, this is all I did to get it to crash 4 times. And this crash does not generate a dmp. 

 

I think I gave up too early when trying to replicate your crash method. I didn't spam it for as long as you did in some of your attempts.

  • Like 1
Link to comment
Share on other sites



Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...