automate valgrind memory leak detection with travis for linux

MadanaGopalThirumalai · MadanaGopalThirumalai · commit dfaf02c07da7 · 2017-03-28T08:59:31.000+05:30
diff --git a/.travis.yml b/.travis.yml
@@ -25,6 +25,7 @@ script:
 - cd $TRAVIS_BUILD_DIR
 - sh build_px.sh "build_$TRAVIS_OS_NAME.sh" "testrunner_$TRAVIS_OS_NAME.sh"
 - if [ "$TRAVIS_OS_NAME" == "linux" ]; then sh pxleakcheck_linux.sh; fi
+- if [ "$TRAVIS_OS_NAME" == "linux" ]; then sh valgrind_linux.sh; fi
 - if [ "$TRAVIS_PULL_REQUEST" == "false" ]; then cd $TRAVIS_BUILD_DIR; fi
 - if [ "$TRAVIS_PULL_REQUEST" == "false" ]; then tar -cvzf logs.tgz logs/* ; fi
 addons:
diff --git a/examples/pxScene2d/src/pxscene.sh b/examples/pxScene2d/src/pxscene.sh
@@ -16,8 +16,23 @@ export LD_LIBRARY_PATH=$PathR
 export NODE_PATH=.
 
 #export RT_LOG_LEVEL=info
- 
+
+if [ $ENABLE_VALGRIND -eq 1 ]
+then
+if [ -z $VALGRINDLOGS ]
+then
+VALGRINDLOGS=valgrind_logs
+fi
+echo "valgrind --tool=memcheck --log-file=$VALGRINDLOGS --leak-check=yes --show-reachable=yes --num-callers=20 --track-fds=yes ./pxscene $1 $2 $3 $4 $5 $6 $7"
+if [ -z $SUPPRESSIONS ]
+then
+valgrind --tool=memcheck --log-file=$VALGRINDLOGS --leak-check=yes --show-reachable=yes --num-callers=20 --track-fds=yes ./pxscene $1 $2 $3 $4 $5 $6 $7
+else
+valgrind --tool=memcheck --suppressions=$SUPPRESSIONS  --log-file=$VALGRINDLOGS --leak-check=yes --show-reachable=yes --num-callers=20 --track-fds=yes ./pxscene $1 $2 $3 $4 $5 $6 $7
+fi
+else
 ./pxscene $1 $2 $3 $4 $5 $6 $7
+fi
 #To run pxscene as background process
 #./pxscene $1 $2 $3 $4 $5 $6 $7 < `tty` >> /var/tmp/pxscene.log 2>&1 &
 
diff --git a/leak.supp b/leak.supp
@@ -0,0 +1,10 @@
+{
+  glutLeaks 
+  Memcheck:Leak
+  match-leak-kinds:definite
+  fun:malloc
+  ...
+  fun:glXMakeContextCurrent
+  fun:fgOpenWindow
+  ...
+}
diff --git a/valgrind_linux.sh b/valgrind_linux.sh
@@ -0,0 +1,54 @@
+#!/bin/sh
+export VALGRINDLOGS=$TRAVIS_BUILD_DIR/logs/valgrind_logs
+export ENABLE_VALGRIND=1
+export PX_DUMP_MEMUSAGE=1
+export SUPPRESSIONS=$TRAVIS_BUILD_DIR/leak.supp
+VALGRINDPXCORELOGS=$TRAVIS_BUILD_DIR/logs/valgrind_pxcore_logs
+
+#run valgrind and monitor for completion
+cd $TRAVIS_BUILD_DIR/examples/pxScene2d/src
+./pxscene.sh testRunner_memcheck.js > $VALGRINDPXCORELOGS &
+grep "RUN COMPLETED" $VALGRINDPXCORELOGS
+retVal=$?
+count=0
+while [ "$retVal" -ne 0 ] &&  [ "$count" -lt 600 ]; do
+sleep 30;
+grep "RUN COMPLETED" $VALGRINDPXCORELOGS
+retVal=$?
+count=$((count+30))
+echo "Valgrind execution going on for $count seconds";
+done
+
+#kill pxscene either after js terminates or no response for 5 minutes
+echo "`ps -ef | grep valgrind |grep -v grep|grep pxscene|grep -v pxscene.sh|awk '{print $2}'`"
+kill -15 `ps -ef | grep valgrind |grep -v grep|grep pxscene|grep  -v pxscene.sh|awk '{print $2}'`
+sleep 5s;
+pkill -9 -f pxscene.sh
+
+#check whether valgrind got completed
+grep "definitely lost" $VALGRINDLOGS
+retVal=$?
+if [ "$retVal" -ne 0 ]
+then
+echo "Valgrind execution got stuck and not terminated in 5 minutes";
+if [ "$TRAVIS_PULL_REQUEST" != "false" ]
+then
+cat $VALGRINDLOGS
+fi
+exit 1;
+fi
+
+#check for memory leak
+grep "definitely lost: 0 bytes in 0 blocks" $VALGRINDLOGS
+retVal=$?
+if [ "$retVal" -eq 0 ]
+then
+exit 0;
+else
+echo "!!!!!!!!!!!!! Memory leak present !!!!!!!!!!!!!!!!!!!";
+if [ "$TRAVIS_PULL_REQUEST" != "false" ]
+then
+cat $VALGRINDLOGS
+fi
+exit 1;
+fi
