Bug 713088

+++ This bug was initially created as a clone of Bug #712894 +++

Description of problem:
There is more allocs then frees and lost bytes when opening an existing man page in man. There is different between only open the man page and close using 'q' and open the man page, scroll to the end and then close using 'q'.

Version-Release number of selected component (if applicable):
man-1.6d-2.el5

How reproducible:
100%

Steps to Reproduce:
1. # valgrind man man (existing man page)
   pres 'q' to exit man
   # valgrind man man
==17183== Memcheck, a memory error detector
==17183== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==17183== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==17183== Command: man man
==17183== 
==17183== 
==17183== HEAP SUMMARY:
==17183==     in use at exit: 176,583 bytes in 149 blocks
==17183==   total heap usage: 235 allocs, 86 frees, 576,038 bytes allocated
==17183== 
==17183== LEAK SUMMARY:
==17183==    definitely lost: 2,046 bytes in 61 blocks       <<<<<<< lost bytes
==17183==    indirectly lost: 85 bytes in 3 blocks
==17183==      possibly lost: 0 bytes in 0 blocks
==17183==    still reachable: 174,452 bytes in 85 blocks
==17183==         suppressed: 0 bytes in 0 blocks
==17183== Rerun with --leak-check=full to see details of leaked memory
==17183== 
==17183== For counts of detected and suppressed errors, rerun with: -v
==17183== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)

2. # valgrind man man (existing man page)
   scroll to the end and pres 'q' to exit man
   # valgrind man man
==17254== Memcheck, a memory error detector
==17254== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==17254== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==17254== Command: man man
==17254== 
==17254== 
==17254== HEAP SUMMARY:
==17254==     in use at exit: 176,583 bytes in 149 blocks
==17254==   total heap usage: 235 allocs, 86 frees, 576,038 bytes allocated
==17254== 
==17254== LEAK SUMMARY:
==17254==    definitely lost: 2,046 bytes in 61 blocks
==17254==    indirectly lost: 85 bytes in 3 blocks
==17254==      possibly lost: 0 bytes in 0 blocks
==17254==    still reachable: 174,452 bytes in 85 blocks
==17254==         suppressed: 0 bytes in 0 blocks
==17254== Rerun with --leak-check=full to see details of leaked memory
==17254== 
==17254== For counts of detected and suppressed errors, rerun with: -v
==17254== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)


Actual results:
lost some bytes after correct closed app 

Expected results:
no lost bytes

--- Additional comment from jmarko on 2011-06-14 10:26:02 CEST ---

same behaviour when opening an non-existing man page. Only when don't open a man page it lost 0 bytes. I have done a test to reproduce it see QA whiteboard.