New Early Access builds
Christian Stein
sormuras at gmail.com
Tue Dec 1 11:31:51 UTC 2020
No, I didn't see them before.
A similar run 3 weeks ago using 16-loom+7-285 [1] didn't emit
those warning messages. A second run today [2] produced them, too,
but fewer in numbers, methinks.
Will keep an eye on those warnings, as GitHub will upgrade their
"Linux boxes" to run Ubuntu-20.04, soon [3].
[1] https://github.com/sormuras/junit5-looming/runs/1389153831#step:10:15
[2] https://github.com/sormuras/junit5-looming/runs/1479300751#step:10:15
[3] https://github.com/actions/virtual-environments/issues/1816
On Tue, Dec 1, 2020 at 12:23 PM Alan Bateman <Alan.Bateman at oracle.com>
wrote:
> On 01/12/2020 10:11, Christian Stein wrote:
> > :
> >
> > The run with 1,000,000 virtual threads emitted some warnings, though.
> > They read like:
> >
> > Warning: [warning][os,thread] Failed to start thread -
> > pthread_create failed (EAGAIN) for
> > attributes: stacksize: 1024k, guardsize: 0k, detached.
> >
> > Are those memory-related issues?
> This looks to be an issue spinning up FJ worker threads. I can't tell if
> it's threads for the common pool or carrier threads used by the default
> scheduler (you will potentially see N or 2*N threads here I think). Have
> you see resource issues on their VMs before?
>
> -Alan
>
More information about the loom-dev
mailing list