CDV ❯ A long held lock which is never requested or released could hold up Lock GC in the L1 and thus cause a memory leak in L1 and in the L2 too.

• Type: Bug
• Status: Closed
• Priority: 2 Major
• Resolution: Fixed
• Component/s:
• Labels:

• Assignee: ssubbiah
• Reporter: ssubbiah
• Created: May 23, 2008
• Votes: 0
• Watchers: 0
• Updated:

  July 27, 2012
• Resolved:

  May 27, 2008

Description

Title says it all.

Mail extract :

I think there is a bug. If L1 has grabed a lock for ever, it will prevent other free locks from getting GCed. So if following conditions meet

1) L1 has a forever lock 2) Same L1 later acquired another lock greedly and releases it once done 3) No other L1 in cluster ask for lock acquired in 2nd step. 4) In this case lock acquired in 2nd step will never be GCed on L1. Basically forever lock kind of halts Lock GC, number of locks held by L1 will keep increasing.

Comments

Saravanan Subbiah 2008-05-27

Fixed in trunk and 2.6 in rev 8640 and 8637.

Hung Huynh 2008-06-02

also merged into the new 2.6 (old 2.6.0)