Opened 10 years ago

Closed 20 months ago

Last modified 4 months ago

#7205 closed bug (fixed)

[mail_daemon] crashed in std::_Rb_tree_increment

Reported by: diver Owned by: bga
Priority: normal Milestone: R1/beta2
Component: Servers/mail_daemon Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


This is hrev40416, gcc4hybrid. I had tried to stop mail_daemon from downloading all of my mail from gmail by quiting it from ProcessController which led to this crash:

Thread 926 caused an exception: Segment violation
[Switching to team /boot/system/servers/mail_daemon (564) thread user thread (926)]
0x007c1c32 in std::_Rb_tree_increment () from /boot/system/lib/
(gdb) bt
#0  0x007c1c32 in std::_Rb_tree_increment () from /boot/system/lib/
#1  0x007c1c8c in std::_Rb_tree_increment () from /boot/system/lib/
#2  0x01bd6fd3 in IMAPMailboxSync::Sync () from /boot/system/add-ons/mail_daemon/inbound_protocols/IMAP
#3  0x01bc8bb3 in IMAPInboundProtocol::Connect () from /boot/system/add-ons/mail_daemon/inbound_protocols/IMAP
#4  0x01bca733 in IMAPInboundProtocol::SyncMessages () from /boot/system/add-ons/mail_daemon/inbound_protocols/IMAP
#5  0x01bc8828 in IMAPInboundProtocol::UpdateSettings () from /boot/system/add-ons/mail_daemon/inbound_protocols/IMAP
#6  0x01bc8e13 in IMAPInboundProtocol::AddedToLooper () from /boot/system/add-ons/mail_daemon/inbound_protocols/IMAP
#7  0x005bdbc6 in MailProtocol::SetProtocolThread () from /boot/system/lib/
#8  0x005bdedd in MailProtocolThread::MessageReceived () from /boot/system/lib/
#9  0x005be3ff in InboundProtocolThread::MessageReceived () from /boot/system/lib/
#10 0x003eea38 in BLooper::DispatchMessage () from /boot/system/lib/
#11 0x003f0574 in BLooper::task_looper () from /boot/system/lib/
#12 0x003f029a in BLooper::_task0_ () from /boot/system/lib/
#13 0x0024e070 in thread_entry () from /boot/system/lib/
#14 0x703cdfec in ?? ()

Change History (3)

comment:1 by diver, 9 years ago

I've just observed it in hrev41828.

comment:2 by waddlesplash, 20 months ago

Resolution: fixed
Status: newclosed

Almost certainly fixed by hrev52647 or one of the preceding commits.

comment:3 by nielx, 4 months ago

Milestone: R1R1/beta2

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone

Note: See TracTickets for help on using tickets.