Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#5630 closed Enhancement (incomplete)

LibEvent 2.0.x have problem async dns leak memory, not fixed

Reported by: DevZone Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.82
Severity: Normal Keywords:
Cc:

Description

libev = http://software.schmorp.de/pkg/libev.html

http://libev.schmorp.de/bench.html

Libev (first released in 2007-11-12) is also a high-performance event loop, supporting eight event types (I/O, real time timers, wall clock timers, signals, child status changes, idle, check and prepare handlers).

It uses a priority queue to manage timers and uses arrays as fundamental data structure. It has no artificial limitations on the number of watchers waiting for the same event. It offers an emulation layer for libevent and optionally the same DNS, HTTP and buffer management (by reusing the corresponding libevent code through its emulation layer).

Change History (2)

comment:1 Changed 8 years ago by jordan

  • Priority changed from Highest to Normal
  • Resolution set to incomplete
  • Severity changed from Major to Normal
  • Status changed from new to closed

Thank you for reporting this bug and helping to make Transmission better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

At a minimum, we need:

  1. the specific steps or actions you took that caused you to encounter the problem,
  2. the behavior you expected, and
  3. the behavior you actually encountered (in as much detail as possible).

Thanks!

comment:2 Changed 8 years ago by x190

Happy programmers fix bugs faster and more efficiently.

So cheer up already! :-)

Note: See TracTickets for help on using tickets.