Opened 9 years ago

Closed 9 years ago

#12043 closed defect (fixed)

MSN segfaults after 1-2 minutes inactivity with the latest MTN snapshot

Reported by: poizon Owned by: QuLogic
Milestone: Component: MSN
Version: Keywords: msn segfault
Cc:

Description


Attachments (3)

gdb.log (17.5 KB) - added by poizon 9 years ago.
gdb backtrace
slplink.c.patch (494 bytes) - added by poizon 9 years ago.
maybe this little patch can fix the problem
Pidgin-vearaport.txt (12.2 KB) - added by plaes 9 years ago.
traceback-with-bt-full.log

Download all attachments as: .zip

Change History (11)

Changed 9 years ago by poizon

gdb backtrace

Changed 9 years ago by poizon

maybe this little patch can fix the problem

comment:1 Changed 9 years ago by poizon

  • Milestone set to 2.7.1

comment:2 Changed 9 years ago by rekkanoryo

  • Milestone 2.7.1 deleted

Do not change the milestone.

comment:3 Changed 9 years ago by darkrain42

  • Status changed from new to pending

That patch absolutely wouldn't change anything; g_free(NULL) is perfectly safe and a no-op (and that isn't even the code that it's crashing in).

Provide a monotone version.

comment:4 Changed 9 years ago by poizon

  • Status changed from pending to new

I have tried this revision: fcca66333eb613450c541e03921f3344a8e9f185

comment:5 follow-up: Changed 9 years ago by elb

Is this reproducible? Does it happen in 2.7.0? Does it happen only under certain circumstances?

Changed 9 years ago by plaes

traceback-with-bt-full.log

comment:6 in reply to: ↑ 5 ; follow-up: Changed 9 years ago by plaes

Replying to elb:

Is this reproducible? Does it happen in 2.7.0? Does it happen only under certain circumstances?

I have also gotten occasional crash with similar backtrace since upgrading to 2.7.0.

One thing I can be sure, that it once happened after the other side of conversation logged out.

comment:7 in reply to: ↑ 6 Changed 9 years ago by QuLogic

Replying to plaes:

I have also gotten occasional crash with similar backtrace since upgrading to 2.7.0.

Shouldn't be related. Please file a new ticket.

comment:8 Changed 9 years ago by QuLogic

  • Resolution set to fixed
  • Status changed from new to closed

There's something wrong with our auto-close script, apparently.

In ba8f17d65062b49bd721597c0993ae3a341365d9,

And another one just like 94fa017925fa206fc36f520ee42c54f57429b4e1. But
this time, the switchboard might not get destroyed immediately, so you'd
get it trying to destroy the slplink when it times out instead.

I think this fixes #12043.
Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!