Bug 99529 - libinput 1.6.0 test failure (valgrind identified memory leaks)
Summary: libinput 1.6.0 test failure (valgrind identified memory leaks)
Status: RESOLVED NOTOURBUG
Alias: None
Product: Wayland
Classification: Unclassified
Component: libinput (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-25 03:43 UTC by Bruce Dubbs
Modified: 2017-01-29 23:48 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Bruce Dubbs 2017-01-25 03:43:04 UTC
==================================================
   libinput 1.6.0: test/test-suite-valgrind.log
==================================================

# TOTAL: 3
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: symbols-leak-test
=======================

==10733== 11 bytes in 1 blocks are definitely lost in loss record 81 of 290
==10733==    at 0x4C2AACD: malloc (vg_replace_malloc.c:299)
==10733==    by 0x46F7BD: xmalloc (xmalloc.c:112)
==10733==    by 0x469598: set_default_locale (locale.c:81)
==10733==    by 0x419950: main (shell.c:411)
==10733==
==10733== 17 bytes in 1 blocks are definitely lost in loss record 112 of 290
==10733==    at 0x4C2AACD: malloc (vg_replace_malloc.c:299)
==10733==    by 0x46F7BD: xmalloc (xmalloc.c:112)
==10733==    by 0x4524EA: make_dev_fd_filename (subst.c:5692)
==10733==    by 0x4524EA: process_substitute (subst.c:5751)
==10733==    by 0x4524EA: expand_word_internal (subst.c:9172)
==10733==    by 0x454E33: shell_expand_word_list (subst.c:10565)
==10733==    by 0x454E33: expand_word_list_internal (subst.c:10688)
==10733==    by 0x42F14E: execute_simple_command (execute_cmd.c:4153)
==10733==    by 0x43134B: execute_command_internal (execute_cmd.c:802)
==10733==    by 0x432BDD: execute_command (execute_cmd.c:405)
==10733==    by 0x41BD51: reader_loop (eval.c:180)
==10733==    by 0x41AAAA: main (shell.c:792)
==10733==
==10734== 11 bytes in 1 blocks are definitely lost in loss record 80 of 291
==10734==    at 0x4C2AACD: malloc (vg_replace_malloc.c:299)
==10734==    by 0x46F7BD: xmalloc (xmalloc.c:112)
==10734==    by 0x469598: set_default_locale (locale.c:81)
==10734==    by 0x419950: main (shell.c:411)
==10734==
==10734== 17 bytes in 1 blocks are definitely lost in loss record 111 of 291
==10734==    at 0x4C2AACD: malloc (vg_replace_malloc.c:299)
==10734==    by 0x46F7BD: xmalloc (xmalloc.c:112)
==10734==    by 0x4524EA: make_dev_fd_filename (subst.c:5692)
==10734==    by 0x4524EA: process_substitute (subst.c:5751)
==10734==    by 0x4524EA: expand_word_internal (subst.c:9172)
==10734==    by 0x454E33: shell_expand_word_list (subst.c:10565)
==10734==    by 0x454E33: expand_word_list_internal (subst.c:10688)
==10734==    by 0x42F14E: execute_simple_command (execute_cmd.c:4153)
==10734==    by 0x43134B: execute_command_internal (execute_cmd.c:802)
==10734==    by 0x432BDD: execute_command (execute_cmd.c:405)
==10734==    by 0x41BD51: reader_loop (eval.c:180)
==10734==    by 0x41AAAA: main (shell.c:792)
==10734==
==10731== 11 bytes in 1 blocks are definitely lost in loss record 82 of 278
==10731==    at 0x4C2AACD: malloc (vg_replace_malloc.c:299)
==10731==    by 0x46F7BD: xmalloc (xmalloc.c:112)
==10731==    by 0x469598: set_default_locale (locale.c:81)
==10731==    by 0x419950: main (shell.c:411)
==10731==
FAIL symbols-leak-test (exit status: 3)
Comment 1 Peter Hutterer 2017-01-29 21:49:12 UTC
looks like these are leaks in bash. we had that in fedora a while ago:
https://bugzilla.redhat.com/show_bug.cgi?id=1241533
Can you please confirm that this is the issue and take it from there. This is definitely not a libinput bug (nothing in the callstack is libinput-related) and I'm struggling for time to chase this one down.
Comment 2 Bruce Dubbs 2017-01-29 23:01:03 UTC
I was using bash 4.4.0.  I'll try to trace down the problem in bash.
Comment 3 Peter Hutterer 2017-01-29 23:48:37 UTC
thanks!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.