Ardour & jackd crashing when opening session

Hello all,
i'm currently encountering a problem with ardour 2.7/2.8 (upgraded to 2.8 to see if my problem was resolved - it is not).

When i try to load my more complex projects (about 15 tracks, with some plugins), Ardour just fails to load at the "signal flows and plugin" step.

I tried to figure out what happened, the terminal does not give much information, and there is no error displayed by Ardour, it just freezes with jack, and i must reboot my system in order to make jack (qjackctl actually) work again.

It seems from the terminal that jack disconnect flows as soon as it has been connected by Ardour (this is my undestanding), read the terminal output below:

Before trying to open the project:
--------------------------------------------------------------------------------------------
WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs
out of memory. You can view the memory limit with 'ulimit -l', and it
is normally controlled by /etc/security/limits.conf

-Ardour is running with more simple projects (1 or 2 tracks)
-I have several projects that do not run properly, the way I described
-When I try to load very old sessions of a dysfunctionning project, it won't run in the same way (this was to make sure I had not performed modifications that recently corrupted the project)
-I tried to disable plugins in the xml file, by commenting "" stuff, it is still crashing the same way
-I used to use Ubuntu Studio Jaunty, and after this problem occured moved to 64 studio beta 3 (based on Ubuntu hardy Heron): the problem is still there
-When I kill Ardour after it's frozen, the system crashes and go to the login page! and I need to restart to get jack working properly

I suppose based on this that the problem is related to Ardour and jackd.

Sorry, my message is not correctly displayed because too long I suppose... I'll try to short it:

Hello all,
i'm currently encountering a problem with ardour 2.7/2.8 (upgraded to 2.8 to see if my problem was resolved - it is not).

When i try to load my more complex projects (about 15 tracks, with some plugins), Ardour just fails to load at the "signal flows and plugin" step.

I tried to figure out what happened, the terminal does not give much information, and there is no error displayed by Ardour, it just freezes with jack, and i must reboot my system in order to make jack (qjackctl actually) work again.

It seems from the terminal that jack disconnect flows as soon as it has been connected by Ardour (this is my undestanding), read the terminal output below:

Before trying to open the project:
--------------------------------------------------------------------------------------------
WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs
out of memory. You can view the memory limit with 'ulimit -l', and it
is normally controlled by /etc/security/limits.conf

-Ardour is running with more simple projects (1 or 2 tracks)
-I have several projects that do not run properly, the way I described
-When I try to load very old sessions of a dysfunctionning project, it won't run in the same way (this was to make sure I had not performed modifications that recently corrupted the project)
-I tried to disable plugins in the xml file, by commenting "" stuff, it is still crashing the same way
-I used to use Ubuntu Studio Jaunty, and after this problem occured moved to 64 studio beta 3 (based on Ubuntu hardy Heron): the problem is still there
-When I kill Ardour after it's frozen, the system crashes and go to the login page! and I need to restart to get jack working properly

I suppose based on this that the problem is related to Ardour and jackd.

Can you create a Mantis issue for this, and attach your console log as seperate txt files and your session file please?

We also would likely need a backtrace, (See the article on Debugging Ardour). At this point I am wondering what plugins you are utilizing as some are known to crash Ardour, but if you could do the above we can take a look at it. Thanks.

I will post my backtrace if the issue is not simple to resolve (I mean, this could be due to a known problem with some plugin).

The plugins I used are specified in the ardour file attached to my report. What make me think that it is not a plugin problem is the fact that it is doing the same with other projects + i did not added new plugins recently + i tried to comment the plugin section in the xml file, and it did not resolve the issue.

WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs
out of memory. You can view the memory limit with 'ulimit -l', and it
is normally controlled by /etc/security/limits.conf

This message is potentially the explanation of all of your issues. Please address it before doing anything else.