Open alexeyknyshev opened 9 years ago
Thanks for the report. I know that there is something fishy going on with memory but sadly I'm not the one who wrote that code. I'm using a fork of NanoVG which implemented display lists to enhance performance, but I think it is not completely bug free yet. (It has not been pulled into NanoVG yet) To trigger a memory fuck-up, open the text editor, and resize it very narrow so that the text will be wrapped to a lot of lines. This will usually cause a crash. I believe all this is linked to the way memory is allocated and reallocated for displayLists (see all ****DisplayList functions in nanovg.c).
Hi, I've run valgrind memory analyzer on kiui_example. Everything below may be missdetected problems. There are some interesting places to check:
Once on startup:
Running example long time, error reported on exit:
And such a lot of similar reports about nvgCreateDisplayList
Regards, Alexey Knyshev