Bug 1244907 - cross-built ld loops and leaks memory randomly during stage2 bootstrap
Summary: cross-built ld loops and leaks memory randomly during stage2 bootstrap
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: binutils
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nick Clifton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: fedora-bootstrap
TreeView+ depends on / blocked
 
Reported: 2015-07-20 18:12 UTC by Jaromír Cápík
Modified: 2016-07-19 17:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 17:06:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jaromír Cápík 2015-07-20 18:12:06 UTC
Description of problem:
During the stage2 bootstrap we sometimes experience the ld process eating 100% cpu and leaking memory so quickly that it's killed automatically after few minutes of such activity.

Due to the nature of the issue it's difficult to collect useful debug data, but the issue is well reproducible in our environment, that is accessible for debugging.

Version-Release number of selected component (if applicable):
binutils-2.24-32.fc21
glibc-2.20-8.fc21
kernel-4.0.0-1.fc22

How reproducible:
randomly

Comment 1 Jaromír Cápík 2015-07-20 18:13:21 UTC
NOTE: In our case we cross-built aarch64 binutils on x86_64 builder.

Comment 2 Carlos O'Donell 2015-07-20 19:13:26 UTC
It reproduces sufficiently that watching the loader you can catch ld doing this behaviour and attach to it with gdb. However, it just looks like ld is stuck processing a linker script.

Comment 3 Fedora End Of Life 2015-11-04 11:04:19 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-12-02 14:35:18 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Fedora End Of Life 2016-07-19 17:06:17 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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