Memory leak in BridgePhaseRenderImpl.cleanup() when BridgeRequestScope is supposed to go out-of-scope

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.1.0-ga1, 3.0.0-legacy-ga1, 3.0.0-ga1, 3.1.0-ga1
• Fix Version/s: 2.1.1-ga2, 3.0.1-legacy-ga2, 3.0.1-ga2, 3.1.1-ga2, 3.2.x
• Component/s: liferay-faces-bridge
• Labels: None
• Similar Issues: Show 5 results ; ;

  FACES-1288	Memory leak when BridgeRequestScope created in RENDER_PHASE of portlet lifecycle
  FACES-1463	References to BridgeRequestScope instances causing memory leak
  FACES-196	BridgeRequestScope not being released/deallocated from memory
  FACES-219	Optimization - assume that developers don't want the BridgeRequestScope preserved at the end of the RenderRequest
  FACES-1257	BridgePhaseRenderImpl.execute() missing null-check in finally clause

This issue was first reported in the forums here:
http://www.liferay.com/community/forums/-/message_boards/message/17234742

Calls to bridgeRequestScopeCache.remove(Object) should pass bridgeRequestScope.getId() instead of the bridgeRequestScope instance itself.

[Thomas Möller]

With the appropriate patch I get now this kind of error: "...[BridgePhaseBaseImpl:247] Found render parameter name=[myportletcom.liferay.faces.bridge.bridgeRequestScopeId] value=[myportlet:::3B5E2024CC867046A0FAFDF3F8648CA5:::1352712628143] BUT bridgeRequestScope is NOT in the cache"

[Thomas Möller]

To reproduce this error you can use my examples from FACES-1446. If you click twice on the submit button you get the error. (The bridge request scope ends with the render phase therefore it does not exist in the second event phase.)

[Neil Griffin]

Hi Thomas,

When you wrote:

With the appropriate patch applied I get now this kind of error

Is this just an annoyance in the server log, or is it breaking the functionality of your portlet?

Thanks,

Neil

[Thomas Möller]

The logged error is annoying but it seems that it does not prevent my application from working.