On 03/16/2016 02:04 AM, Kinkie wrote:
> On Tue, Mar 15, 2016 at 9:43 PM, Alex Rousskov wrote:
>> On 03/14/2016 02:11 PM, Kinkie wrote:
>>> this second attempt at bug4438 tries a different approach: by giving
>>> MemBlob its own pools and having a hard initialization dependency in
>>> MemBlob's
On Tue, Mar 15, 2016 at 9:43 PM, Alex Rousskov
wrote:
> On 03/14/2016 02:11 PM, Kinkie wrote:
>
>> this second attempt at bug4438 tries a different approach: by giving
>> MemBlob its own pools and having a hard initialization dependency in
>> MemBlob's
On 03/14/2016 02:11 PM, Kinkie wrote:
> this second attempt at bug4438 tries a different approach: by giving
> MemBlob its own pools and having a hard initialization dependency in
> MemBlob's allocating function, instead of relying on memAllocString.
Forgive me if I missed how this decision