Bug 149319 - top crashes when terminal window is resized
top crashes when terminal window is resized
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: procps (Show other bugs)
3
All Linux
medium Severity low
: ---
: ---
Assigned To: Karel Zak
Brian Brock
:
: 150580 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-02-22 08:03 EST by Per Steinar Iversen
Modified: 2007-11-30 17:11 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-03-17 07:54:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Per Steinar Iversen 2005-02-22 08:03:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5)
Gecko/20050117 Fedora/1.7.5-3

Description of problem:
On x86_64: Start top in xterm windows. Resize the window continously,
eventually top dies with the message:

*** glibc detected *** realloc(): invalid next size:
0x000000000062b310 ***

The long hex number in the error message seems to be different each time.

If top is started this way there is more info:

MALLOC_CHECK_=1 top

*** glibc detected *** realloc(): invalid pointer: 0x000000000060f520 ***
*** glibc detected *** malloc(): memory corruption: 0x0000000000610970
*** 

Version-Release number of selected component (if applicable):
procps-3.2.3-5.1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Start top in terminal windows
2. Resize the window a number of times
3. Eventually top dies
    

Actual Results:  top dies

Expected Results:  top should continue to run

Additional info:

This happens on both i686 and x86_64
Comment 1 Karel Zak 2005-03-17 05:59:32 EST
*** Bug 149616 has been marked as a duplicate of this bug. ***
Comment 2 Karel Zak 2005-03-17 06:00:43 EST
*** Bug 150580 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.