This is a regression in listed projects
Mon, Aug 12
cool. i saw those :) let's call this done for now.
Sun, Aug 11
Regarding other findings
Right now am concentrating on reducing number of memory allocation and string parsing during startup time as well as memory consumption ( unnecessary ) . Will tag you when I raise a patch or bug against it.
I saw your patch already landed in master. Awesome :)
yeah. actually found bug #2 in that patch. i still have one of my unlocked funcs still lock. forgot to remove them... now down to .... 28 locks to start elm test. so... update. locally with an updated patch... 615604 -> 28 lock+unlock cycles. i think... that will be good enough eh? :) even if a read lock is 3x as expensive... we do it 0.004% as much as before, and still get the write contention improvements. :) i call this a win.
cool. so i guessed what you wanted. btw that patch has a small bug in it. find it :) (i already have and fixed it locally). it won't affect running things and testing performance though.
Sat, Aug 10
btw... that should actually be faster than the original spinlock before rwlock as it's even less lock+unlocks. as it's a rwlock multiple readers will not block each-other unlike spinlocks too. only a writer will end up blocking others and that path i have left as-is.
so do you mean something like: P319
nah - just a performance thing and it's not a huge one... it's only in some code paths. so not showstopper
Jul 25 2019
Jul 13 2019
Jul 11 2019
False alarm, dunno what it was.
Jul 9 2019
Yes, that fixed it, thanks.
Jul 7 2019
Jun 29 2019
Jun 20 2019
Jun 19 2019
Jun 3 2019
Here's the invalid access part:
May 30 2019
This is new and I have not been able to reproduce it here. Could you run it through valgrind and post a trace?
May 23 2019
May 22 2019
May 20 2019
not sure, but in efl_canvas_gesture_private.h, there is the inclusion of a source file :
May 14 2019
Apr 30 2019
Apr 23 2019
Indeed, works for me!
Apr 10 2019
Mar 28 2019
Mar 25 2019
let me fix this.
This job is just a trick optimization to avoid several sizing() calls in one frame.
Actually, this is not mandatory we can revert code if it harms image behavior.
Mar 23 2019
Okay, cause found!
A little bit more debugging information: this is related to elm_image, if you replace the elm_icon part in the test_icon.c with a direct evas_image, then everything is fine, no lacking, by the time you make it a elm_image, the lacking starts to happen.
Mar 22 2019
A little bit of debugging information: this is fully related to images. You can replace the icons in the genlist with a button or label, and there is no lacking.