Project

General

Profile

Actions
Copy link

Bug #2516

closed

UdpChannel::newPeer does not properly handle error condition

Added by Alex Afanasyev almost 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Alex Afanasyev
Category:
Faces
Target version:
v0.4
Start date:
02/12/2015
Due date:
% Done:

100%

Estimated time:

Description

When UdpChannel is destroyed, newPeer is called with error==cancelled. There could be other error conditions upon which no processing should take place inside the method.

Related issues 1 (0 open — 1 closed)

Blocks NFD - Bug #2517: NFD state is not properly cleaned up on destructionAbandoned

Actions
Actions
Copy link
 #1

Updated by Alex Afanasyev almost 10 years ago

  • Status changed from Resolved to Code review
  • % Done changed from 0 to 100
Actions
Copy link
 #2

Updated by Alex Afanasyev almost 10 years ago

  • Blocks Bug #2517: NFD state is not properly cleaned up on destruction added
Actions
Copy link
 #3

Updated by Alex Afanasyev almost 10 years ago

I cannot come up with a feasible test case. This bug was causing error intermittently (depending on what random value goes into UdpChannel::m_newRemoteEndpoint).

Actions
Copy link
 #4

Updated by Junxiao Shi almost 10 years ago

  • Status changed from Code review to Closed
Actions
Copy link

Also available in: Atom PDF