[
https://issues.apache.org/jira/browse/YETUS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102503#comment-15102503
]
Colin Patrick McCabe commented on YETUS-286:
--------------------------------------------
We can definitely tune the concurrency level of make... or use cgroups as
[~andrew.wang] has suggested.
However, even assuming that we ran out of memory because of running too many
{{make}} processes at once, I don't understand how that would lead to a
{{failed to map segment from shared object: Permission denied}} error. This
corresponds to the POSIX error code {{EACESS}}. If we couldn't allocate
memory, I would expect to see {{Cannot allocate memory}}, which corresponds to
{{ENOMEM}}. Or I would expect to see the OOM killer send a SIGKILL, which
would lead to "Terminated" messages. Perhaps I am missing something, but I am
having a hard time seeing how running out of memory or CPU would cause
"Permission denied" errors.
> The native build randomly fails with "failed to map segment from shared
> object"
> -------------------------------------------------------------------------------
>
> Key: YETUS-286
> URL: https://issues.apache.org/jira/browse/YETUS-286
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Affects Versions: 0.2.0
> Reporter: Colin Patrick McCabe
> Assignee: Sean Busbey
> Priority: Critical
>
> On Jenkins, the native build seems to intermittently fail with "failed to map
> segment from shared object." For example:
> {code}
> [WARNING] /usr/bin/cmake: error while loading shared libraries: libxml2.so.2:
> failed to map segment from shared object: Permission denied
> {code}
> We have also seen this happen with {{librtmp.so.0}}, {{libcurl.so.4}}, and
> other native libraries which are dependencies of the thing being built.
> Basically, there is some random chance any particular native dependency will
> get "failed to map segment." When this happens, the native build fails and
> returns a -1 even if there was no actual problem. This requires us to re-run
> Jenkins to get a correct result. The problem does not seem to reproduce
> locally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
