Skip to content
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

Open
dstodev opened this issue Feb 22, 2025 · 7 comments
Open

UHK80 "Messenger message pool space ran out" #1144

dstodev opened this issue Feb 22, 2025 · 7 comments

Comments

@dstodev
Copy link

dstodev commented Feb 22, 2025

Hello,

My UHK80 is configured like:

  • Latest firmware (12.3.5)
  • With batteries, but connected to PC via USB-C cable
  • With bridge cable connected

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!":

Image

Resetting the halves via reset button on the back fixed the issue for now.

@kareltucek
Copy link
Collaborator

Thanks for the report!

We know about it, although we are still in the dark as to the exact cause.

@mhantsch
Copy link
Contributor

BTW, @kareltucek , there's a typo in the message. "Messanger" => "Messenger"... not the most pressing issue, I know 😉

@kareltucek
Copy link
Collaborator

Actually, given its etymology and knowing myself, I don't think it is a typo ☺️

@Zetaphor
Copy link
Member

Zetaphor commented Feb 26, 2025

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

@Zetaphor
Copy link
Member

I also just noticed my error is identical except for where their screenshot shows R 15, mine shows R 16

@wallacewinfrey
Copy link

wallacewinfrey commented Feb 26, 2025

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 R 50. Prior to both, the keyboard stopped responding. Same environment as OP.

@nref
Copy link

nref commented Feb 27, 2025

Happened to me just now as well on firmware 12.3.5. Same message but with R 14 on the display.

I was typing a chat message and it started repeating the a key. No modifiers pressed. My keyboard has batteries. Normally unplugging it will make the keyboard turn off. In this state, it stayed on. Pressing the reset button fixed it.

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.

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

6 participants