Quassel IRC

benjamb wrote:

If I drag one chat over another in an attempt to merge the buffers, but decline the prompt, I hit a segmentation fault. This doesn't seem to happen every time, but I have reproduced and captured a backtrace.
https://www.mymilestoneecard.com
I was actually attempting to reorder chats, but that's not really relevant.

Hello,

you're encountering a segmentation fault in a graphical/chat interface application when dragging one chat over another — possibly a crash related to buffer management or drag-and-drop event handling. Since it doesn't happen every time, it may be due to a race condition, uninitialized pointer, or improper state handling after declining the merge.

To help further, I’ll need more context. Specifically:

Which application or environment is this? (Is it a custom app, a known messaging app, etc.?)

What does the backtrace show? If you have a gdb or other debugger backtrace, please paste it here.

Is this reproducible with steps? Even a rough sequence of actions could help.

Do you have debug symbols or source access?

Even without all details, based on your description, some possible root causes include:

UI state inconsistency: The application might not fully reset or correctly handle the cancelation of the merge, leading to use-after-free or null pointer dereference when the drag operation completes.

Double-free or invalid memory access: Especially likely if memory buffers representing chats are destroyed or invalidated upon merge attempt — and that logic isn’t fully rolled back when you decline.

Drag-and-drop buffer mismanagement: The buffer being moved may have pointers or references that remain active or get corrupted.