On Sun, Mar 6, 2016 at 9:41 PM, Alex Rousskov
wrote:
> On 03/06/2016 11:16 AM, Kinkie wrote:
>
>> As I cannot reproduce the issue it's really hard to do a root cause analysis.
>
> Agreed. However, if you can make SBuf/MemBlob use memory pools before
> those pools
On 03/06/2016 11:16 AM, Kinkie wrote:
> As I cannot reproduce the issue it's really hard to do a root cause analysis.
Agreed. However, if you can make SBuf/MemBlob use memory pools before
those pools are initialized, then we do have a bug worth fixing (even if
Yuri does not suffer from that
On 03/06/2016 02:15 PM, Kinkie wrote:
> On Sun, Mar 6, 2016 at 9:41 PM, Alex Rousskov wrote:
>> On 03/06/2016 11:16 AM, Kinkie wrote:
> Having the MemBlob pools be static
> members of the MemBlob class will guarantee proper initialization
> before even the first MemBlob is instantiated, won't it?
On Sat, Mar 5, 2016 at 10:21 PM, Alex Rousskov
wrote:
> On 03/05/2016 04:31 AM, Kinkie wrote:
>> ensuring that mempools are initialized before MemBlob is
>> used.
>
> Please explain how
>
> * a call to Mem::Init()
>
> at some random time during dynamic