Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python3a5 compile failing due to high memory usage #47269

Closed
segfaulthunter mannequin opened this issue May 31, 2008 · 3 comments
Closed

Python3a5 compile failing due to high memory usage #47269

segfaulthunter mannequin opened this issue May 31, 2008 · 3 comments
Labels
build The build process and cross-build

Comments

@segfaulthunter
Copy link
Mannequin

segfaulthunter mannequin commented May 31, 2008

BPO 3019
Nosy @birkenfeld
Files
  • output: Output of various commands.
  • gdb_output: Output of GDB
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2008-05-31.21:29:18.767>
    created_at = <Date 2008-05-31.18:32:49.443>
    labels = ['build']
    title = 'Python3a5 compile failing due to high memory usage'
    updated_at = <Date 2008-05-31.21:29:18.716>
    user = 'https://bugs.python.org/segfaulthunter'

    bugs.python.org fields:

    activity = <Date 2008-05-31.21:29:18.716>
    actor = 'georg.brandl'
    assignee = 'none'
    closed = True
    closed_date = <Date 2008-05-31.21:29:18.767>
    closer = 'georg.brandl'
    components = ['Build']
    creation = <Date 2008-05-31.18:32:49.443>
    creator = 'segfaulthunter'
    dependencies = []
    files = ['10488', '10490']
    hgrepos = []
    issue_num = 3019
    keywords = []
    message_count = 3.0
    messages = ['67585', '67587', '67589']
    nosy_count = 2.0
    nosy_names = ['georg.brandl', 'segfaulthunter']
    pr_nums = []
    priority = 'normal'
    resolution = 'duplicate'
    stage = None
    status = 'closed'
    superseder = None
    type = 'compile error'
    url = 'https://bugs.python.org/issue3019'
    versions = ['Python 3.0']

    @segfaulthunter
    Copy link
    Mannequin Author

    segfaulthunter mannequin commented May 31, 2008

    I have tried building Python3a5 today using the tarball offered on your
    internet site.
    The process './python -E setup.py build' keeps on allocating my memory
    using more than 80% of my RAM, I am certain that it would have used more
    if I had not cancelled it.
    When I use ltrace to track the system calls and put it into the
    Makefile, the resource usage still raises but much slower, if I use
    ltrace and supply it a PID, the memory usage raises as fast as normal. I
    think this is due to something in ltrace, it's understandable because it
    produced a file of more than 600MB.

    I attached an excerpt of the output of ltrace, showing you how the
    system calls seem to repeat, and the output of './configure', 'make',
    'uname -a', 'lspci' and 'lsmod' so you have some data about my system.
    I also got a screenshot showing the output of htop, make and strace
    together: http://img516.imageshack.us/img516/2275/screenshot1ab8.png.
    Maybe the output of two different programs(ltrace and strace) will help
    you too.
    I tried out building the current SVN py3k branch, resulting in a similar
    problem.
    PS: It would help if you allowed uploading of multiple files to bug reports

    @segfaulthunter segfaulthunter mannequin added build The build process and cross-build labels May 31, 2008
    @segfaulthunter
    Copy link
    Mannequin Author

    segfaulthunter mannequin commented May 31, 2008

    Added the output of GDB as the memory usage was nearing 70%.
    Hope it helps.

    @birkenfeld
    Copy link
    Member

    Turns out this is due to GCC 4.3 being used. Dupe of bpo-2626.

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    build The build process and cross-build
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant