Anyone else getting lots of sudden crashes in 8.1.4?

[Sly One]

Since 8.1.4, Live on Windows has been just disappearing suddenly (none of the usual C++ runtime errors a la previous 8.1.x versions) with no apparent pattern as to when. The undo buffer recovery works again (hooray) but is usually a few edits behind.

Have been sending off bug reports to the Abes most of the time, but want to reassure myself that this isn't just me...

[robbiePie]

Sly and Abes,
I have sent off three bug reports in the last half hour. I stopped sending them after that...

Live has been consistently crashing on me whenever I go to midi map mode when the Max4Live (Step Sequencer-GM Drum Sequencer) is loaded as a default template . I just installed 8.1.4 and Max For Live a few days ago. Before then I barely EVER had crashes.

The crash occurrs every time I started up. I deleted preferences.cfg and it continued to crash. I removed the M4L step sequencer and saved a new default template. Restarted Live. I am able to midi map without crashes. Now I add the M4L step sequencer and now I can go to midi map mode WITHOUT crashing. I save the set, restart Live, load the saved set with the M4L midi effect it and I can still call midi map mode WITHOUT crashes.

I just repeated the error. If a user creates a default template with the M4L Step Sequencer enabled, starts into live using that template, and then types CMD-M for midi map mode (Im on a mac) Live will crash.

The Apple problem report has this to say about the exceptions:

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000014a
Crashed Thread: 0

Thread 0 Crashed:
0 com.ableton.live 0x0112e180 std::out_of_range::~out_of_range() + 1032668
1 com.ableton.live 0x00d6fab1 std::invalid_argument::~invalid_argument() + 1471475
2 com.ableton.live 0x00d6fb96 std::invalid_argument::~invalid_argument() + 1471704
3 com.ableton.live 0x00d65dfe std::invalid_argument::~invalid_argument() + 1431360
4 com.cycling74.patcher 0x1fb634d7 WiresPrivate::milf_device_get_current_assignment_labels(WiresPrivate::_milf_device*) + 153
5 com.cycling74.patcher 0x1fb636e7 Wires::StartMidiAssignment() + 177
6 com.ableton.live 0x00d695f2 std::invalid_argument::~invalid_argument() + 1445684
7 com.ableton.live 0x003b1ca5 0x1000 + 3869861
8 com.ableton.live 0x003c495b 0x1000 + 3946843
9 com.ableton.live 0x003c4619 0x1000 + 3946009
10 com.ableton.live 0x01096608 std::out_of_range::~out_of_range() + 411236
11 com.ableton.live 0x0157e181 std::out_of_range::~out_of_range() + 5554653
12 com.ableton.live 0x0147a000 std::out_of_range::~out_of_range() + 4489308
13 com.ableton.live 0x0148d1a8 std::out_of_range::~out_of_range() + 4567556
14 com.apple.AppKit 0x96b4ae8f -[NSApplication sendAction:to:from:] + 112
15 com.apple.AppKit 0x96bf9b64 -[NSMenu performActionForItemAtIndex:] + 493
16 com.apple.AppKit 0x96bf9869 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 220
17 com.apple.AppKit 0x96bf94ef -[NSMenu performKeyEquivalent:] + 866
18 com.apple.AppKit 0x96bf7d94 -[NSApplication _handleKeyEquivalent:] + 492
19 com.apple.AppKit 0x96b14ac7 -[NSApplication sendEvent:] + 3997
20 com.ableton.live 0x01486792 std::out_of_range::~out_of_range() + 4540398
21 com.apple.AppKit 0x96a71fe7 -[NSApplication run] + 867
22 com.ableton.live 0x0148cf36 std::out_of_range::~out_of_range() + 4566930
23 com.ableton.live 0x0147c482 std::out_of_range::~out_of_range() + 4498654
24 com.ableton.live 0x00002652 0x1000 + 5714
25 com.ableton.live 0x00002579 0x1000 + 5497

If this is an array out of bounds issue... eesh.

Thoughts?