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/06/12 00:20:26 UTC

[jira] Commented: (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:comment-tabpanel#action_12503656 ] 

Andrew Black commented on STDCXX-440:
-------------------------------------

A resolution for this issue has been committed in the referenced subversion change.  However, I do not believe this will be the final solution.

This solution uses the ulimt function of the exec utility to limit tests to allocating 1 GB of memory.  In addition, I chose to limit examples to allocating 256 MB of memory.

A similar limit should be applied for the locale tests, but I am uncertain as to what a suitable number would be.

One concern I have is that users are unable to override this value, as the --ulimit switch operates on a last takes precedence mode of operation.  The resolution to this concern would be to prepend the switch to the runflags variable.

A second concern I have is that some previous successful tests may now segfault due to being unable to allocate the memory they require.  Manual testing on my local box indicates that the 22_codecvt_iso2022 test (not yet in subversion) exhibits this behavior.

--Andrew Black

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