I ran unity8 through valgrind with massif, with the commands
stop unity8 export MIR_SERVER_NAME=session-0 export MIR_SOCKET=/run/mir_socket export QT_QPA_PLATFORM=mirserver valgrind --tool=massif --time-unit=ms --detailed-freq=1 /usr/bin/unity8
attached is a visualization of the data. unity8 was not touched.
It appears there's 2 sources of memory leaks, both appear on the android side.
I ran unity8 through valgrind with massif, with the commands
stop unity8 NAME=session- 0 /run/mir_ socket PLATFORM= mirserver
export MIR_SERVER_
export MIR_SOCKET=
export QT_QPA_
valgrind --tool=massif --time-unit=ms --detailed-freq=1 /usr/bin/unity8
attached is a visualization of the data. unity8 was not touched.
It appears there's 2 sources of memory leaks, both appear on the android side.