-
Notifications
You must be signed in to change notification settings - Fork 71
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
UHK80 "Messenger message pool space ran out" #1144
Comments
Thanks for the report! We know about it, although we are still in the dark as to the exact cause. |
BTW, @kareltucek , there's a typo in the message. "Messanger" => "Messenger"... not the most pressing issue, I know 😉 |
Actually, given its etymology and knowing myself, I don't think it is a typo |
Another datapoint, USB connect to the right side, batteries disconnected, just got this error for the first time. Also running 12.3.5 Keyboard has been on and in use all day, I had noticed later in the day I was getting some occasional but inconsistent sluggishness in responding to layer keys. Hard reset by unplugging and replugging USB fixed it |
I also just noticed my error is identical except for where their screenshot shows |
Have gotten this message twice now, I didn't take note of the values on the second line the first time, but did the second time. My message was the same, with the only difference being mine showed |
Happened to me just now as well on firmware 12.3.5. Same message but with I was typing a chat message and it started repeating the I installed 12.3.5 a few days ago, up from 12.3.1, so it seems like a regression between those versions. Fellow dev here, so I understand how these things go. Thanks for an awesome keyboard. |
Hello,
My UHK80 is configured like:
When I was playing a game earlier, using the WASD keys, the S key got stuck continually being emitted, and then the board stopped responding.
The display on the right half displays the message "Messenger message pool space ran out!":
Resetting the halves via reset button on the back fixed the issue for now.
The text was updated successfully, but these errors were encountered: