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

["Martin Sebor (JIRA)" <ji...@apache.org>]

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

Martin Sebor commented on STDCXX-440:
-------------------------------------

I spent some time looking at this problem a bit and it seems to me that the loop in the limit_process() function in exec.cpp that's (presumably) supposed to iterate over all the limits hardcoded in the body of the function, skipping those that weren't set on the command line, instead appears to break after finding the first one that's not set. Since the first one is RLIMIT_CORE and the only one we're setting is last (RLIMIT_AS), the function never does set any limit. That seems really strange because the function hasn't changed since it was implemented in http://svn.apache.org/viewvc?view=rev&revision=452253 and I don't see how it could have ever worked.

Incidentally, parse_limit_opts() in cmdopt.cpp hardcodes the same set of limits as limit_process(), which means that if we update one of them (e.g., add a new limit) we'll need to remember to update the other, which is all too easy to forget to do. The data in both functions should be factored out into a common data structure shared by the function to eliminate this potential problem.

> 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.