Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

regex compilation leaks memory when warnings are made FATAL #15205

Open
p5pRT opened this issue Feb 29, 2016 · 6 comments
Open

regex compilation leaks memory when warnings are made FATAL #15205

p5pRT opened this issue Feb 29, 2016 · 6 comments

Comments

@p5pRT
Copy link

p5pRT commented Feb 29, 2016

Migrated from rt.perl.org#127632 (status was 'open')

Searchable as RT127632$

@p5pRT
Copy link
Author

p5pRT commented Feb 29, 2016

From @khwilliamson

There are a number of places where there are potential memory leaks, especially in parsing bracketed character classes. SVs are allocated, and when a warning occurs they don't get cleaned up.
--
Karl Williamson

@p5pRT
Copy link
Author

p5pRT commented Mar 1, 2016

From @khwilliamson

On Sun Feb 28 21​:52​:10 2016, khw wrote​:

There are a number of places where there are potential memory leaks,
especially in parsing bracketed character classes. SVs are allocated,
and when a warning occurs they don't get cleaned up.

There should be an audit done for where these occur.
--
Karl Williamson

@p5pRT
Copy link
Author

p5pRT commented Mar 1, 2016

From [Unknown Contact. See original ticket]

On Sun Feb 28 21​:52​:10 2016, khw wrote​:

There are a number of places where there are potential memory leaks,
especially in parsing bracketed character classes. SVs are allocated,
and when a warning occurs they don't get cleaned up.

There should be an audit done for where these occur.
--
Karl Williamson

@p5pRT
Copy link
Author

p5pRT commented Jun 5, 2017

From @jkeenan

On Tue, 01 Mar 2016 22​:22​:37 GMT, khw wrote​:

On Sun Feb 28 21​:52​:10 2016, khw wrote​:

There are a number of places where there are potential memory leaks,
especially in parsing bracketed character classes. SVs are allocated,
and when a warning occurs they don't get cleaned up.

There should be an audit done for where these occur.

How would we go about detecting such memory links and conducting such an audit?

Thank you very much.

--
James E Keenan (jkeenan@​cpan.org)

@p5pRT
Copy link
Author

p5pRT commented Jun 5, 2017

The RT System itself - Status changed from 'new' to 'open'

@p5pRT
Copy link
Author

p5pRT commented Jun 8, 2017

From @khwilliamson

On 06/05/2017 12​:58 PM, James E Keenan via RT wrote​:

On Tue, 01 Mar 2016 22​:22​:37 GMT, khw wrote​:

On Sun Feb 28 21​:52​:10 2016, khw wrote​:

There are a number of places where there are potential memory leaks,
especially in parsing bracketed character classes. SVs are allocated,
and when a warning occurs they don't get cleaned up.

There should be an audit done for where these occur.

How would we go about detecting such memory links and conducting such an audit?

Thank you very much.

I'm talking about code reading perhaps augmented with experimentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants