I apologize for my rant.
I've got valgrind running on my unity-panel-service now, by doing this:
sudo mv /usr/lib/unity/unity-panel-service
/usr/lib/unity/unity-panel-service.real
sudo ln -sf unity-panel-service.wrap /usr/lib/unity/unity-panel-service
cat <<"EOF" | sudo tee -a /usr/lib/unity/unity-panel-service.wrap
#!/bin/sh
me=${0##*/}
rname="$me.real"
real=$(which "$rname" 2>/dev/null)
[ -z "$real" ] || { [ -x "${0%/*}/${rname}" ] && real="${0%/*}/$rname"; }
[ -n "$real" ] || { echo "FAILED TO FIND real: ${rname}"; exit 1; }
G_SLICE=always-malloc G_DEBUG=gc-friendly \
exec valgrind -v --tool=memcheck --leak-check=yes --num-callers=38 \
--log-file=${HOME:-/tmp}/${USER:+${USER}-}${me}.log \
"$real"
EOF
sudo chmod 755 /usr/lib/unity/unity-panel-service
(most of that is just for my future reference. i will post back with more info).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974382
Title:
memory leak in unity-panel-service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/974382/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
