Re: [Jack-Devel] superweird jack error

Hi Gabriel and everybody,

as I wrote in my earlier post the same thing happened when I just tried to connect jack_simple_client so it's definitely jack that's trying to allocate all that memory.

I don't remember turning on a "profile" option but I'll recomompile and turn debug on. Maybe this will give some more info.

Btw., two of the memory numbers in the error

Cannot lock down 68157440 byte memory area (Cannot allocate memory)
Cannot lock down 2048917504 byte memory area (Cannot allocate memory)
Cannot lock down 25165824 byte memory area (Cannot allocate memory)

are the exact same numbers somebody else with the same error got here:

http://linux-audio.4202.n7.nabble.com/jack2-32bit-vs-64bit-td42373.html

Everybody there seemed to assume it had to do with 32 bit vs 64 bit operation. But there is no 64 bit stuff at all on my computer.

Cheers,
Axel


On Mar 16, 2013, at 6:31 PM, Gabriel M. Beddingfield wrote:

> Hi Axl,
> 
> On 03/14/2013 01:48 PM, [hidden] wrote:
>> The stick has 1 gbyte or ram. Top tells me:
>> 
>> KiB Mem:    863396 total,   208044 used,   655352 free,    15204 buffers
>> KiB Swap:        0 total,        0 used,        0 free,   121640 cached
>> 
>> But why in the world would jackd want to lock down 2048917504 byte
>> (about 2 gbyte) of ram?
>> 
>> Btw., the --no-mlock option doesn't seem to exist in jackd2.
> 
> From your logs it kind of looked like SC was trying to allocate all that memory... but I may have misunderstood.
> 
> Anyway, jack2 has a compile option for run-time performance metrics (configure with "--profile", I think).  If enabled, it has to lock down gobs of memory for storing run-time events.  The only way to disable it is to recompile JACK without it.  Did you happen to enable it?
> 
> -gabriel
> 
> 
> 

1363467778.15002_0.ltw:2,a <0F1E023E-5A98-4F0F-A7F0-4B6BE86B372C at freenet dot de>