Bug 712894

Summary:	man more allocs then frees when opening an existing man page and definitely lost bytes
Product:	Red Hat Enterprise Linux 5	Reporter:	Juraj Marko <jmarko>
Component:	man	Assignee:	Peter Schiffer <pschiffe>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	5.7	CC:	nlevinki
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	713088 920157 (view as bug list)		Environment:
Last Closed:	2013-01-10 17:29:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	713088, 920157

Description Juraj Marko 2011-06-13 13:59:21 UTC

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

Comment 1 Juraj Marko 2011-06-14 08:26:02 UTC

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.

Comment 2 Juraj Marko 2011-06-14 09:39:51 UTC

same problem in rhel6 so I clone the bug for rhel6

Comment 3 RHEL Program Management 2011-09-23 00:54:12 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 4 Peter Schiffer 2013-01-10 17:29:29 UTC

I'm closing this bug. Man package probably won't be updated again in RHEL-5 this late in development cycle. Also, this problem is fixed in RHEL-6.

peter