Am 03.02.2017 um 16:26 schrieb William F Pokorny:
> On 02/03/2017 10:05 AM, William F Pokorny wrote:
>> On 02/03/2017 05:17 AM, ThH wrote:
>>
>> On Ubuntu 16.04 (Boost 1.58) tracked the seg fault to commit: 756cba6
>> Sun Jan 31 00:32:25 2016 +0100
>>
>> "Added support for increased thread stack sizes when boost 1.50 or later
>> is used."
>>
>> Was about to try bumping up the requested thread stack sizes some.
>>
> 
> Working in commit
> 
> it seems like changing:
> 
> taskThread = NewBoostThread(boost::bind(&Task::TaskThread, this,
> completion), 1024 * 1024 * 2);
> 
> to:
> 
> taskThread = NewBoostThread(boost::bind(&Task::TaskThread, this,
> completion), 1024 * 1024 * 4);
> 
> in source/backend/support/task.cpp
> 
> gets past the seg fault. Let me see if the same change fixes our master
> at 3.7.2...  It does.
> 
> As for a real fix, not sure the path we should take?

That's a tricky one: No matter what value we actually choose here, it
will always be possible to write /some/ more or less pathological scene
that triggers this type of crash.

But what we certainly should do is replace the hard-coded value with a
macro, which we can then define in the platform-specific compile-time
config of the backend module. This way, any user running into such a
problem at least has the opportunity to build their own modified binary.

Post a reply to this message