topic Re: Yocto Qt application touch generate memory leak in i.MX Processors

Yocto Qt application touch generate memory leak

arkceajin — Fri, 19 Jun 2015 09:54:30 GMT

Guys, i need help, i successfully compiled the Yocto, when i try to run a empty Qt application, only contain a QWindow, and keep touching screen about five minutes.
then as touching, memory usage keep increasing, finally monitor to black, looks like Linux terminal console.

So i guess the Yocto GUI and my little Demo is crash, but the Linux core still running.

OS: Poky ( Yocto Project Reference Distro ) 1.6.2

Board: i MAX6Q

Could anyone tell me what wrong with my Yocto, is this a BUG?

Thanks forward

Re: Yocto Qt application touch generate memory leak

igorpadykov — Tue, 23 Jun 2015 00:06:28 GMT

Hi ark

please look at simple Qt hellow world tutorial

http://cache.freescale.com/files/training/doc/dwf/QT_IMX6.pdf

then one can follow sect.5.6.7 Qt5 attached document

from L3.14.28_1.0.0_iMX6QDLS_BUNDLE

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

Re: Yocto Qt application touch generate memory leak

arkceajin — Tue, 23 Jun 2015 09:13:00 GMT

Hello Igor

I reviewed the document and attachment. Sorry still not get the point.

The error message log show as below:

[1943670.533] (II) XINPUT: Adding extended input device "Advanced Silicon S.A. CoolTouch(TM) System" (type: TOUCHSCREEN, id 9)
[1943670.533] (II) evdev: Advanced Silicon S.A. CoolTouch(TM) System: initialized for absolute axes.
[1943670.534] (**) Advanced Silicon S.A. CoolTouch(TM) System: (accel) keeping acceleration scheme 1
[1943670.534] (**) Advanced Silicon S.A. CoolTouch(TM) System: (accel) acceleration profile 0
[1943670.534] (**) Advanced Silicon S.A. CoolTouch(TM) System: (accel) acceleration factor: 2.000
[1943670.534] (**) Advanced Silicon S.A. CoolTouch(TM) System: (accel) acceleration threshold: 4
(EE) 
(EE) Backtrace:
(EE) 
(EE) Segmentation fault at address 0x68
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
  at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.

Re: Yocto Qt application touch generate memory leak

igorpadykov — Tue, 23 Jun 2015 11:55:29 GMT

Hi ark

will memory leak disappear if you remove touch driver ?

~igor

Re: Yocto Qt application touch generate memory leak

arkceajin — Wed, 24 Jun 2015 01:37:53 GMT

Hi igor

Memory leak wont occur if i use mouse.

memory usage keep increasing as i touching screen continuously, if i stop touching ,the memory increasing also stop.

Ark

Re: Yocto Qt application touch generate memory leak

igorpadykov — Wed, 24 Jun 2015 04:11:43 GMT

Hi ark

you can try to debug with memory leak detection tools

QT mem leak

http://www.qtcentre.org/threads/56705-Qt-amp-Memory-Leak

Memory Debuggers - eLinux.org

~igor

Re: Yocto Qt application touch generate memory leak

arkceajin — Thu, 25 Jun 2015 10:01:29 GMT

Hello igor

Sorry i didn't explain briefly.

Every program crash, no matter the one i created or Yocto one.

If i run program which i created, Yocto GUI and the program both crash except Linux core.

If i run Yocto original program, Whole Yocto crashed.

igor

Re: Yocto Qt application touch generate memory leak

igorpadykov — Thu, 25 Jun 2015 11:32:30 GMT

Hi ark

please read link below

Yocto Training - HOME

How to Test Yocto for i.MX6

also you can apply to training

Open Source Yocto y Freescale|Freescale

if this is custom board it may be recommended to run ddr test

https://community.freescale.com/docs/DOC-96412

~igor

Re: Yocto Qt application touch generate memory leak

arkceajin — Fri, 26 Jun 2015 07:57:59 GMT

Hi igor

We found out the bug which cause memory leak.

The problem happen in XInput2 lib.

So we change to XInput1 lib, the problem solved.

ark