You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by "Andrew Black (JIRA)" <ji...@apache.org> on 2007/09/25 19:39:50 UTC

[jira] Resolved: (STDCXX-440) 23_allocator test case can consume all system memory

     [ https://issues.apache.org/jira/browse/STDCXX-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Black resolved STDCXX-440.
---------------------------------

    Resolution: Fixed

Resolving issue as Fixed.  The latest subversion change fixes the misbehavior observed.   This change has been verified under manual testing.  I think the reason this bug wasn't spotted before was because the only limit being set with any regularity was RLIMIT_CORE, which is the first limit which was being checked in the loop.

Refactoring the common data shared between parse_limit_opts() and limit_process() is outside the scope of this issue and should probably be filed as an enhancement for 4.2.1.

If it is necessary to reevaluate the limits being set, this issue can be reopened.

> 23_allocator test case can consume all system memory
> ----------------------------------------------------
>
>                 Key: STDCXX-440
>                 URL: https://issues.apache.org/jira/browse/STDCXX-440
>             Project: C++ Standard Library
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 4.2
>         Environment: RHAP 5 (possibly others)
>            Reporter: Eric Lemings
>            Assignee: Andrew Black
>            Priority: Critical
>             Fix For: 4.2
>
>         Attachments: sample-top.txt
>
>
> The 22_allocator test case has been observed to consume all primary and virtual memory bringing the unfortunate system to its knees.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.