Jira (PUP-1689) Windows Memory Leaks
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1689 Windows Memory Leaks Change By: Moses Mendoza Labels: needs_repro triaged windows Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1689) Windows Memory Leaks
Title: Message Title John Duarte commented on PUP-1689 Re: Windows Memory Leaks Closing this due to age. If the issue is rediscovered, please re-open Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1689) Windows Memory Leaks
Title: Message Title John Duarte updated an issue Puppet / PUP-1689 Windows Memory Leaks Change By: John Duarte Labels: needs_repro triaged windows Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1689) Windows Memory Leaks
Title: Message Title Kenaz Kwa updated an issue Puppet / PUP-1689 Windows Memory Leaks Change By: Kenaz Kwa Team: Agent & Platform Support Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1689) Windows Memory Leaks
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1689 Windows Memory Leaks @ethan is this still a concern given some of the memory stuff we've added with FFI? Change By: Rob Reynolds Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1689) Windows Memory Leaks
Title: Message Title Ethan Brown created an issue Puppet / PUP-1689 Windows Memory Leaks Issue Type: Bug Affects Versions: 3.4.2 Assignee: Unassigned Created: 13/Feb/14 3:11 PM Fix Versions: 4.x Priority: Normal Reporter: Ethan Brown We noticed an increasing number of failures on the Windows 2008R2 spec box in Jenkins, and speculated this was due to memory pressure. The machine was bumped from 2GB to 4GB and the problems went away. It seems evident that despite our efforts to trigger Ruby garbage collection, that we are leaking memory that is causing issues when running these tests. This ticket is a bit vague, but an effort to better profile Puppet and search out memory allocation issues with a combination Windbg + debug versions of Ruby and/or the CRT is in order. See https://tickets.puppetlabs.com/browse/QA-836
