https://bugs.kde.org/show_bug.cgi?id=422261
Mark Wielaard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Status|REPORTED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Mark Wielaard <[email protected]> --- Thanks for the report. It seems I accidentally introduced this bug with: commit f15beea767892ae52ed1d92d789114685fb5dc82 Author: Mark Wielaard <[email protected]> Date: Sat May 25 16:31:02 2019 +0200 Fix memory leak in launcher-linux.c When the clientname argument is not a full absolute path we reconstruct the full path using $PATH. This reconstructed full path would be leaked. This is small and insignificant. But valgrind should give a good example. So free the path again when we are done and allocated the memory. Also don't print the path twice in the debug output if we didn't need to construct a new different path for it. I am not sure why this wasn't noticed earlier because your example clearly shows it failing. I guess 32-on-64 arch runs are just not done that much or always involve a relative or absolute path? -- You are receiving this mail because: You are watching all bug changes.
