Ticket #287 (accepted bug)

Opened 16 months ago

Last modified 4 months ago

Trunk warnings: "...Handles still allocated"

Reported by: jayesh Owned by: goodell
Priority: major Milestone: mpich2-1.3
Component: mpich2 Keywords:
Cc:

Description (last modified by balaji) (diff)

When I run pt2pt/scancel & some io tests on trunk I get the following message when compiled with "--enable-strict --enable-g=all",

shakey:/sandbox/jayesh/freshBuild/mpich2/test/mpi/pt2pt> mpiexec -n 2 scancel
 No Errors
In direct memory block for handle type REQUEST, 3 handles are still allocated

Regards, Jayesh

Attachments

Change History

Changed 14 months ago by gropp

This is indicating that there is a bug in the handling of cancel of send requests - the requests aren't properly being freed. I checked the test code, and the test code is not at fault.

Changed 12 months ago by balaji

  • milestone set to mpich2-1.1.1

Changed 10 months ago by balaji

  • description modified (diff)

Changed 9 months ago by thakur

  • milestone changed from mpich2-1.1.1 to mpich2-1.1.2

Changed 6 months ago by balaji

  • milestone changed from mpich2-1.1.2 to mpich2-1.2

Milestone mpich2-1.1.2 deleted

Changed 5 months ago by balaji

  • owner set to goodell
  • status changed from new to assigned

I believe Dave is looking into these errors.

Changed 4 months ago by goodell

  • status changed from assigned to accepted

I've got a bead on this, although the proper fix might be more intrusive and riskier than we are willing to tolerate for a bug-fix release like 1.2.1. I'll update this ticket when I know more.

In general, this investigation makes it very clear that the rules for reference counting requests are not obvious or documented anywhere easy to find. We need to remedy this by formulating a coherent strategy for request refcounting, documenting it in the wiki and in code comments, and auditing the current code to make sure that we are following this. Requests are the most commonly created/destroyed object in MPICH2 and properly managing their lifecycle is essential to avoid serious memory leaks.

Changed 4 months ago by goodell

  • milestone changed from mpich2-1.2.1 to mpich2-1.3

Moving to 1.3. The fix for this case will almost certainly have some subtle bug in it that we don't want to introduce for a minor release like this.

WARNING! You need to enter your email address here before you can create or edit tickets. Otherwise the ticket will get treated as spam.

Add/Change #287 (Trunk warnings: "...Handles still allocated")

Author



Change Properties
Action
as accepted
 
Note: See TracTickets for help on using tickets.