On Wednesday 08 Feb 2006 19:17, Emanuel Rumpf wrote: Any chance you can get a stack trace of where it's called? One way to do this would be to add the line assert(0);

at the top of MappedPluginSlot::~MappedPluginSlot(). That should cause a crash in the sequencer process and (probably) show the KDE debug window with a stack trace in it when the crash happens. That won't tell us the whole story, because the stack trace will only be for the sequencer process (it won't indicate what the GUI process tried to get the sequencer to do) but it should get us somewhere... Of course, this will only work if MappedPluginSlot::~MappedPluginSlot() is never called except in the "incorrect" situation. I just added an assert(0) call to the function in my copy, and I found that the call never seems to be reached in normal use, so I think this should be a safe assumption.