You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "A. Dukhovniy (JIRA)" <ji...@apache.org> on 2018/02/19 13:53:00 UTC

[jira] [Created] (MESOS-8594) Mesos master crash (under load)

A. Dukhovniy created MESOS-8594:
-----------------------------------

             Summary: Mesos master crash (under load)
                 Key: MESOS-8594
                 URL: https://issues.apache.org/jira/browse/MESOS-8594
             Project: Mesos
          Issue Type: Bug
          Components: master
    Affects Versions: 1.5.0, 1.6.0
            Reporter: A. Dukhovniy


Mesos master crashes under load. Attached are some infos from the `lldb`:
{code:java}
Process 41933 resuming
Process 41933 stopped
* thread #10, stop reason = EXC_BAD_ACCESS (code=2, address=0x7000089ecff8)
frame #0: 0x000000010c30ddb6 libmesos-1.6.0.dylib`::_Some() at some.hpp:35
32 template <typename T>
33 struct _Some
34 {
-> 35 _Some(T _t) : t(std::move(_t)) {}
36
37 T t;
38 };
Target 0: (mesos-master) stopped.
(lldb)
{code}

To quote [~abudnik] 
{quote}
it’s the stack overflow bug in libprocess due to a way `internal::send()` and `internal::_send()` are implemented in `process.cpp`
{quote}





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)