Session fails to load tr1::bad_weak_ptr

Installation & Configuration Linux
#1

Hi,
I have a session that I properly closed yesterday when finishing my work.
This morning I wanted to load the session and I get this:
image

This is on the console:

Log Messages:
INFO: AlsaAudioBackend: adjusted output channel count to match device.
INFO: AlsaAudioBackend: adjusted input channel count to match device.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
ERROR: AlsaSeqMidiIO: Device initialization failed.
WARNING: AlsaMidiOut: failed to open midi device '144:0'.
ERROR: AlsaSeqMidiIO: Device initialization failed.
WARNING: AlsaMidiIn: failed to open midi device '144:0'.
ERROR: AlsaSeqMidiIO: Device initialization failed.
WARNING: AlsaMidiOut: failed to open midi device '145:0'.
ERROR: AlsaSeqMidiIO: Device initialization failed.
WARNING: AlsaMidiIn: failed to open midi device '145:0'.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaAudioBackend: cannot acquire realtime permissions.
INFO: harvid version: 803
INFO: Loading menus from /opt/Ardour-6.9.0/etc/ardour.menus
ERROR: Unexpected exception during session setup: tr1::bad_weak_ptr

I have looked through the .ardour file and cannot see anything that would pop to my eye. I have a .bak file and compared that to the .ardour but there are only two minor changes for midi-automation. And I have tested to load the .bak, it produces the same error.
Other sessions that I have worked on yesterday DO load and I also can create new sessions.
Anyone any clue?
Best regards,
Robert

#2

Are you sure your Audio/Midi backend is up and running? According to the messages this is not the case (at least MIDI). The exception might be a resulting problem.

#3

as I wrote, I can load other sessions, in fact, I didn’t find any that doesn’t load except this one.
And I also rebooted my system … just to make sure :wink:
And with regards to the MIDI devices, all MIDI devices I have connected are used in almost all my other sessions.

#4

Sorry, I have overseen that other sessions load without problems. But I guess you don’t have this “Device initialization failed” messages when loading other sessions - right?

#5

What version of Ardour is this? If you didn’t get it from this site, does it still happen with the demo version from this site?

Seablade

#6

Your official 6.9
Ardour 6.9.0
“After Bach”
(rev 6.9)
Intel 64-bit

If I can help with analysis like gdb stacktraces etc. let me know

#7

Does it open if you open the session in ‘safe mode’ (disabling plugins)?

Seablade

#8

Nope, safe mode does not change the behaviour.
I also found out: If I confirm the dialog with the error message, Ardour presents the LRU sessions open dialog, if I pick any of the other sessions that do load, Ardour just terminates.

ERROR: Unexpected exception during session setup: tr1::bad_weak_ptr

Set cursor set to default
Segmentation fault (core dumped)
#9

I think you are going to need to make a bug report on Mantis (Bug Tracker) and attach your session file to see if anyone can replicate the issue.

  Seablade
#10

Okay, I will do that.
Shall I file two bug reports? One for the session that doesn’t open and a second with the stacktrace for the segmentation fault?

#11

No, please put that all in one for now, as they are likely related.

#12

Here you go 0008911: Session doesn't load (ERROR: Unexpected exception during session setup: tr1::bad_weak_ptr) - MantisBT
If you need the complete folder in order to load that session, let me know, I will then make that available.
Thanks and regards,
Robert

#13

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.