Ticket #1264 (closed bug: fixed)

Opened 12 years ago

Last modified 12 years ago

Memory leak on sub call

Reported by: quietfanatic Owned by:
Priority: normal Milestone:
Component: none Version: trunk
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:

Description

This affects at least revision 42403.

The following loop shows a large memory leak when a sub is invoked. This leak makes running certain realtime applications impossible.

.sub 'main'

lab:

'foo'() goto lab

.end .sub 'foo' .end

Attachments

leak Download (65 bytes) - added by quietfanatic 12 years ago.
Since newlines were lost in the formatting I have attached the program as a file

Change History

Changed 12 years ago by quietfanatic

  • attachment leak Download added

Since newlines were lost in the formatting I have attached the program as a file

Changed 12 years ago by chromatic

On Wednesday 11 November 2009 13:36:55 Parrot wrote:


>- This affects at least revision 42403.
>
>  The following loop shows a large memory leak when a sub is invoked.  This
>  leak makes running certain realtime applications impossible.
>
>  .sub 'main'
>    lab:
>      'foo'()
>      goto lab
>  .end
>  .sub 'foo'
>  .end

I can't confirm this with Valgrind and Parrot's --leak-test flag, so we do 
release the memory on process exit, but it's clear that something continues to 
allocate more memory if I watch the process in top.  I'll continue to 
investigate.

-- c

Changed 12 years ago by chromatic

  • status changed from new to closed
  • resolution set to fixed

I believe I've fixed this in commits r42427, r42428, r42430, and r42431. Thanks for the report.

Note: See TracTickets for help on using tickets.