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

[Text] (Web-based showcase) Emoji example "text_unicode" freezes up after enough emojis are clicked #3249

Closed
evanrinehart opened this issue Aug 18, 2023 · 4 comments · Fixed by #3250

Comments

@evanrinehart
Copy link

This issue is for the web-hosted emoji example on the raylib website. I could not trigger it on desktop builds of the example.

Click many different emojis and eventually the program stops responding. The number of tries and position of final triggering emoji seems to be random, which makes sense because the program is randomized.

Clicking the same set of working emojis over and over doesn't seem to trigger it. Every time it happens, it was a click on an emoji that was not clicked before. If nothing on the first set of emojis triggers the freeze, press space and try the second set.

I was able to reproduce it on Chrome on OSX, and on Firefox on Ubuntu. The two computers have very different specs so I would be surprised if it was a resource exhaustion issue.

In the screenshot of the frozen program I tried to click on the blue emoji.

image

@evanrinehart evanrinehart changed the title [Text] (Web-based showcase) Emoji example "text_unicode" freezes up sometimes when an emoji is clicked [Text] (Web-based showcase) Emoji example "text_unicode" freezes up after enough emojis are clicked Aug 18, 2023
@ghost
Copy link

ghost commented Aug 18, 2023

Was able to reproduce the issue:

img

Apparently there's an unescaped line break somewhere on examples/text/text_unicode.c.

@raysan5
Copy link
Owner

raysan5 commented Aug 18, 2023

@evanrinehart @ubkp I reproduced it on web and tried to reproduce it on desktop but not possible. This is a compelx example provided by a contributor long time ago. I'm afraid the cost to review it to find the platfomr-dependant issue could be considerable and sincerely I think it does not work it, it's just an example to be used as a reference.

If anyone is ready for that task, I'll keep this issue open for a while but if not, I'm closing it.

@ghost
Copy link

ghost commented Aug 18, 2023

@raysan5 I'm working on #3231, but, if you don't mind keeping this open for a few days, I can take a look at it after that.

@raysan5
Copy link
Owner

raysan5 commented Aug 18, 2023

@ubkp Ok, thank you very much, just take it easy, it could be tricky and the work required for this platform-specific issue probably does not worth the time invested.

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

Successfully merging a pull request may close this issue.

2 participants