View Issue Details

IDProjectCategoryView StatusLast Update
0003364ardourbugspublic2020-04-19 20:14
Reportermoshisushi Assigned Tocth103  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Target Version3.0-beta1 
Summary0003364: Crash when step editing after region deletion
DescriptionSteps to reproduce the problem:

1. Create a MIDI track and connect you MIDI keyboard to it
2. Turn on 'Step edit' for the MIDI track
3. Press some keys on you keyboard to record a couple of notes
4. Delete the region you recorded
5. Repeat step 3
6. Ardour crashes with a segmentation fault:

Program received signal SIGSEGV, Segmentation fault.
0x000000000087757a in ARDOUR::Region::position (this=0x2e00000030) at ../libs/ardour/ardour/region.h:108
108 sframes_t position () const { return _position; }
Additional InformationFull backtrace:

#0 0x000000000087757a in ARDOUR::Region::position (this=0x2e00000030) at ../libs/ardour/ardour/region.h:108
0000001 0x0000000000d09f54 in MidiRegionView::step_add_note (this=0x7fffdc427ef0, channel=0 '\000', number=60 '<', velocity=32 ' ', pos=16, len=0.25)
    at ../gtk2_ardour/midi_region_view.cc:1461
#2 0x0000000000d3ef68 in MidiTimeAxisView::check_step_edit (this=0x297b670) at ../gtk2_ardour/midi_time_axis.cc:948
#3 0x0000000000a5402d in Editor::check_step_edit (this=0x1ce0850) at ../gtk2_ardour/editor.cc:5220
0000004 0x0000000000a84047 in sigc::bound_mem_functor0<bool, Editor>::operator() (this=0x7fffdc36a5d8) at /usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:1787
0000005 0x0000000000a7cd56 in sigc::adaptor_functor<sigc::bound_mem_functor0<bool, Editor> >::operator() (this=0x7fffdc36a5d0)
    at /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:251
#6 0x0000000000a75f89 in sigc::internal::slot_call0<sigc::bound_mem_functor0<bool, Editor>, bool>::call_it (rep=0x7fffdc36a5a0)
    at /usr/include/sigc++-2.0/sigc++/functors/slot.h:103
#7 0x00007ffff236ee02 in ?? () from /usr/lib/libglibmm-2.4.so.1
0000008 0x00007ffff2f7309b in ?? () from /lib/libglib-2.0.so.0
0000009 0x00007ffff2f728c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
0000010 0x00007ffff2f76748 in ?? () from /lib/libglib-2.0.so.0
0000011 0x00007ffff2f76c55 in g_main_loop_run () from /lib/libglib-2.0.so.0
0000012 0x00007ffff1a01bb7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
0000013 0x00007ffff57f0f13 in Gtkmm2ext::UI::run (this=0x17ecfb0, old_receiver=...) at ../libs/gtkmm2ext/gtk_ui.cc:259
0000014 0x0000000000ce0d4f in main (argc=1, argv=0x7fffffffda28) at ../gtk2_ardour/main.cc:433
TagsNo tags attached.

Activities

cth103

2010-08-04 00:06

administrator   ~0008702

I believe this has been fixed. Is it still an issue for you?

moshisushi

2010-08-04 08:13

reporter   ~0008709

Nope, works fine now!

cth103

2010-08-04 09:43

administrator   ~0008710

Thanks!

system

2020-04-19 20:14

developer   ~0022180

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2010-07-26 22:32 moshisushi New Issue
2010-08-03 23:07 cth103 cost => 0.00
2010-08-03 23:07 cth103 Target Version => 3.0-beta1
2010-08-04 00:06 cth103 Note Added: 0008702
2010-08-04 00:06 cth103 Status new => feedback
2010-08-04 08:13 moshisushi Note Added: 0008709
2010-08-04 09:43 cth103 Note Added: 0008710
2010-08-04 09:43 cth103 Status feedback => resolved
2010-08-04 09:43 cth103 Resolution open => fixed
2010-08-04 09:43 cth103 Assigned To => cth103
2020-04-19 20:14 system Note Added: 0022180
2020-04-19 20:14 system Status resolved => closed