Bug 642329
Summary: | invalid fastbin entry (free) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Petr Muller <pmuller> |
Component: | glibc | Assignee: | Andreas Schwab <schwab> |
Status: | CLOSED NOTABUG | QA Contact: | qe-baseos-tools-bugs |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5.6 | CC: | drepper, ebachalo, fweimer, gsim, iboverma, jneedle, kim.vdriet, mfranc, ohudlick, pmuller, snagar |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 593396 | Environment: | |
Last Closed: | 2011-08-17 11:35:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Muller
2010-10-12 15:23:58 UTC
We are seeing this both in 5.5 and 5.6 candidate glibc. Given that this issue was quite urgent for RHEL6, I'm proposing this to be fixed in RHEL5 too. We are actually seeing these aborts on i386 architecture only, and in about 30-40% of testcase runs: we run it in a loop and if the testcase does not crash in 30 seconds, we kill it and re-run: #!/bin/bash PASS=0 FAIL=0 for index in `seq 20` do echo "=== Launching ===" ./test1 & echo "=== Sleeping ===" sleep 30 echo "=== Killing ===" kill $! if [ "$?" == "0" ] then PASS=$(( PASS + 1)) else FAIL=$(( FAIL + 1)) fi sleep 2 done echo "PASSES: $PASS" echo "FAILES: $FAIL" gives something like this in few iterations: === Launching === === Sleeping === terminate called after throwing an instance of 'terminate called after throwing an instance of 'std::bad_alloc' std::bad_alloc' what(): St9bad_alloc what(): St9bad_alloc loopa.sh: line 6: 14590 Aborted ./test I forgot to mention the glibc version: We saw this on: glibc-2.5-49.el5_5.5.i686 glibc-2.5-54.i686 Also, please note that on RHEL5, you need to use g++44 to compile the second testcase, because the original RHEL5 gcc does not know the required -std=c++0x Why do you think this has anything to do with bug #593396? This error check does not even exist in RHEL-5. That appears to be just a case of transient out-of-memory situation. This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update. Contact your manager or support representative in case you need to escalate this bug. Doesn't look like this is a bug. (In reply to comment #6) > Doesn't look like this is a bug. I agree. IMHO the test case completely exhaust virtual address space. It doesn't happen every time only because of random function. Feel free to close it. |