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

Assertion "lookup_hash_table" fails on ToDo App example #30

Closed
qertoip opened this issue Jun 17, 2022 · 6 comments · Fixed by #144
Closed

Assertion "lookup_hash_table" fails on ToDo App example #30

qertoip opened this issue Jun 17, 2022 · 6 comments · Fixed by #144
Labels
bug Something isn't working
Milestone

Comments

@qertoip
Copy link

qertoip commented Jun 17, 2022

** (flet:31142): CRITICAL **: 10:04:19.347: void update_pressing_state(FlKeyEmbedderResponder *, uint64_t, uint64_t): assertion 'lookup_hash_table(self->pressing_records, physical_key) == 0' failed

This happens on the console while playing with the ToDo App example w/o modifications. The GUI seems functional.

@FeodorFitsner
Copy link
Contributor

Could you provide more info please? What OS are you running the example on? What command did you user to run it? Screenshot with an error would help too. Thanks!

@qertoip
Copy link
Author

qertoip commented Jun 20, 2022

Linux with the latest stable Python. The error message I cited just repeats itself on the terminal with no further details. Should be easy to recreate by just running unmodified ToDo App example and doing anything in the GUI. Again, the GUI works despite assertion failures.

@FeodorFitsner
Copy link
Contributor

I'm testing it on Ubuntu 20.04 (though Python is 3.8, not the latest) and it looks "good":

image

What distro/version of Linux are you running it on? Could you catch the steps to reproduce?

@qertoip
Copy link
Author

qertoip commented Jun 21, 2022

Please just press and hold any key in the top text field, entering something like aaaaaaaaaaaaaaaaaaaaa.

I am on the fully updated Arch Linux but that is probably not the key factor.

@FeodorFitsner
Copy link
Contributor

Indeed, I can reproduce the issue in such a way:

image

@FeodorFitsner
Copy link
Contributor

Looks like it's going to be fixed in the next Flutter 3.1 release: flutter/flutter#104870 (comment)

Will close this issue when it's released and the fix is verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants