M1NG

> @fishbowlforever Thanks for reporting, could you reproduce this issue on Windows 10? It sounds like platform dependant... > > In any case, I'm afraid I don't have a HighDPI...

> This issue is caused by the document not being [synchronized](https://github.com/100askTeam/100ask_lvgl_docs) yet. I will synchronize it as soon as possible in the next few days. lvgl.100ask.net首页js有问题，会卡死浏览器

well done, but you forgot something such as Hikvision, DJI, ZTE, Bytedance, kylix linux......

@kisvegabor Can I create this pull request to implement flushing display buffer without callback? ```c diff --git a/src/core/lv_refr.c b/src/core/lv_refr.c index 33aed28aa..86a2976b6 100644 --- a/src/core/lv_refr.c +++ b/src/core/lv_refr.c @@ -1260,6 +1260,9 @@...

> Hi, > > Calling `SDL_UpdateTexture(menu, NULL, buf, 640 * 4);` 30 times in a sec even if nothing happened on the screen (i.e. no rendering happened) seems wasteful. Isn't...

> I see. As a workaround, would it wok if you set an empty `flush_wait_cb` with `lv_display_set_flush_wait_cb`? This way LVGL will use the wait_cb instead of `lv_display_flush_ready`. First, Thank you...

> I'd even go farther to assert that using `atexit` in luv is _invalid_ for the luv module because it is guaranteed to be dynamically linked at runtime **and, more...

Maybe try making some changes? Like calling luv_work_cleanup explicitly. I could submit a pull request, but I'd like to get a thorough discussion with the project maintainers before do that.

It's a good idea to let Lua's gc handle it, and it is also forward compatible, about atexit, maybe they didn't foresee today's situation at that time. just do it...