Solved LCD display contents corruption
-
@Pablo-J.-Rogina I haven't run any other application on my test bench yet. I will have to do that.
-
Further to this post, I continued to analyse the problem.
I wanted to isolate the problem around framebuffer-display driver. I did convert the framebuffer contents to an image to verify what is being displayed in the LCD. I see that, frame buffer contents exactly matches with what is being displayed. So looks like, as @mvuori mentioned, there could be memory leaks which might contribute for this problem.
Today I am going to run valgrind by attaching my application and run overnight and see if there are any leaks in the system.
-
Any more thoughts on this problem?
@SGaist Any comments?
-
Hi,
What backend are you using ?
-
@SGaist Can you please explain a bit more on what you meant by backend?
Linux based system built on AM3358 TI Sitara with Qt 4.8.4. Is that what you have meant Sam? -
Hi
backend info could also include if you are using X11, or directFB or
which method is used for the gfx part / display manager etc. -
@mrjj Thanks for the explanation.
Since this is Embedded Qt, I am don't think it involves X11. I believe that, it uses Linux framebuffer for the rendering.
-
Hi guys!
I should share the good news.
This problem is pretty close to what @mvuori pointed out. I did run a valgrind and I could see lot of leaks.
Instead of focusing on fixing the leaks, I did add a piece of code to leak more memory more often. This was to flood the memory. I can see that, UI contents gets corrupted after the memory gets full.And the black spots / patches on the screen are also linked with the same problem.
So I think this solves the problem. I should build a clean system without memory leaks!
Thanks a lot guys! Special thanks to @mvuori for giving the right clue! I will be happy to mark this post as solved.
--Kumara
-
@kumararajas said in LCD display contents corruption:
So I think this solves the problem. I should build a clean system without memory leaks!
That should generally be your goal oO
I'm glad you were able to narrow the issue down, good luck hunting those leaks.
-
@J.Hilk Thank you :)