Comment 2 for bug 972369

Revision history for this message
Roman (m01brv) wrote :

Although the crash itself is 100% reproducible, the backtrace that I have attached here is not very stable, however.
I often get just a useless single line "0x00000000 in ?? ()" instead of this.
And once I got a single line "0x02009e1d in _vq_lengthlist__44c5_s_p2_0 () from /usr/lib/i386-linux-gnu/libvorbisenc.so.2", which also does not look very reliable.
As if exiting from wicd-kde causes some serious memory corruption, so that even the stack might get corrupted.