Bug #566
Segfault on network disconnect
0%
Description
I didn't try to reproduce it.
Here's what I did:- changed a server's connection options while being connected (port and SSL option)
- disconnected from that network using the context menu in the buffer view
- BAM
Distro: gentoo x86
Quasselclient version: 0.4.0 x86
Quasselcore version: 0.3.1-g734d4c9 amd64
Qt version: 4.4.2
CXXFLAGS=-O2 -ggdb -march=prescott -pipe -fno-omit-frame-pointer -mfpmath=sse -fvisibility-inlines-hidden
Automatic stacktrace attached.
Related issues
History
#1 Updated by Sputnick about 15 years ago
- File Quassel-Crash-20090218-2025.log Quassel-Crash-20090218-2025.log added
- File Quassel-Crash-20090311-1834.log Quassel-Crash-20090311-1834.log added
- File Quassel-Crash-20090311-0756.log Quassel-Crash-20090311-0756.log added
- File Quassel-Crash-20090317-2137.log Quassel-Crash-20090317-2137.log added
- Status changed from New to Confirmed
- Priority changed from Normal to High
- Version changed from 0.3.1+ to 0.4.0+
This trace shows up in some varieties, according to user feedback also sometimes triggered by temporarily hiding multiple buffers, or by selecting Connect or Disconnect from the network context menu. Seems to be related by Qt trying to repaint/resize the BufferView in a bad moment. More traces pointing to most probably that same issue attached.
#2 Updated by Sputnick about 15 years ago
- Target version set to 0.4.2
- Version changed from 0.4.0+ to 0.3.0.x
Bug #663 contains a) a real usable backtrace and b) a way that allows me to reproduce now :)
#3 Updated by Sputnick almost 15 years ago
- Target version changed from 0.4.2 to 0.4.3
#4 Updated by Sputnick over 14 years ago
- Target version deleted (
0.4.3)
#5 Updated by johu about 14 years ago
- Status changed from Confirmed to Feedback
please give feedback, if this is resolved with quassel 0.5.2 or higher
#6 Updated by johu over 13 years ago
- Status changed from Feedback to Closed
No feedback was given within 5 months.