You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the answer on StackOverflow was correct - it was creation of a whole lot of little strings that was causing the problem. The code to handle escape sequences was taking the URL, calling scan, map, and join on a character-by-character basis (even for non-escape sequences). I've modified it to use gsub only on escape sequences. The existing tests pass, and my pathological test posted on StackOverflow went from:
Some speculation at http://stackoverflow.com/questions/20385767/finding-the-cause-of-a-memory-leak-in-ruby
The text was updated successfully, but these errors were encountered: