@User sample updated...and crashing 😉

great! 👍

a way to avoid crash is to...remove some components of second.xml

the more components you have on second.xml, the more you'll crash

I don't know if it's related to memory available or not....on my mac, it crashes at 42 components

no problem at 41

ill check it out, do you have the modified sample?

yes, I shared it on https://filebin.net/odshbn5ofmfisgc3

oh yeah, didnt get the email notification yet 🙂

no problem, I didn't know if you were available or not, so I shared it on forum and discord

Let me know if you need somethings else like testing or similar

well, i can make it crash every time by adding loads of labels in second.xml... i doubt very much its memory... but at least i can get it to break... ...

So you need more than 42 to crash on your side!? Very strange....

actually, i can make it crash with no labels, it just takes more time

Ohh

@User - can you pull latest haxeui-hxwidgets and hxWidgets and see if thats fixed?

i think its fixed... at least, i cant make it crash anymore

build in progress 😉

Good morning

@User is this blank ok to use? https://github.com/haxeui/haxeui-blank

@User sorry, I was locked on a meeting... none of my test projects crashed !!

it seems it's fixed

🤞

wonderful!

for information, to be complete, it didn't fix bug 2, which crash app when listview is removed

it seems it's not related, sadly

i havnt used a mac in about 16 years.... but.... linux has a nifty little monitor called conky.... i assume mac has something maybe similar.... that can be used to monitor memory usage. I have noticed on my end at least, using html5 backend, very little memory gets used outside of what the browser itself already eats up.... what is bug 2 ? i'lll test and see if i can spot something in particular about it on my end.

the 2nd bug in my sample app

It's easier for Ian to test if the bug comes from haxeui or myself like this 😉