Modify

Ticket #6321 (closed Bugs: fixed)

Opened 2 years ago

Last modified 2 years ago

non-paged pool memory leak in win_iocp_io_service

Reported by: Uri Avni <uri@…> Owned by: chris_kohlhoff
Milestone: To Be Determined Component: asio
Version: Boost 1.48.0 Severity: Problem
Keywords: asio windows non-paged pool Cc:

Description

This program takes 2GB of non-paged pool memory after several seconds:

boost::asio::io_service io;
while (1) 
{
 io.run();
 io.reset();
}

When outstanding_work_==0, calls to either run, run_one, poll or poll_one leak a non-paged pool memory, caused by the PostQueuedCompletionStatus?(iocp_.handle, 0, 0, 0) call in win_iocp_io_service::stop()

Attachments

Change History

comment:1 Changed 2 years ago by chris_kohlhoff

(In [76432]) Fix non-paged pool "leak" on Windows when io_service is repeatedly run without anything to do. Refs #6321.

comment:2 Changed 2 years ago by chris_kohlhoff

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

(In [76516]) Merge from trunk:

  • Chrono support.
  • Added object_handle support.
  • Need to enable the basic_handle class when object_handle is supported.
  • Update copyright notices.
  • Fix MSVC "performance warning".
  • Fix for NetBSD. Fixes #6098.
  • Fix regression in buffered_write_stream. Fixes #6310.
  • Fix deadlock on Mac OS X. Fixes #6275.
  • On linux, connect can return EAGAIN in certain circumstances. Remap to another error so that it doesn't look like a non-blocking operation. Fixes #6048.
  • Fix non-paged pool "leak" on Windows when io_service is repeatedly run without anything to do. Fixes #6321.
  • Disable object_handle on Windows CE.
  • Add extra include required for OVERLAPPED struct.
  • Fix doxygen comments.
  • Update documentation.
  • Add missing class.
  • Update copyright year.
View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.