Skip to content

Trying to reproduce a possible memory leak in oboe.js

Notifications You must be signed in to change notification settings

JuanCaicedo/oboe-memory-bug

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

oboe-memory-bug

Trying to reproduce the bug outlined in jimhigson/oboe.js#68.

Getting started

  • $ git clone https://github.com/JuanCaicedo/oboe-memory-bug.git
  • $ cd oboe-memory-bug
  • $ npm install
  • $ npm start

Two conditions

  1. If you go to http://localhost:3000/home, your browser might crash. Chrome displays an "Aw, snap!" error.

  2. If you go to http://localhost:3000/home?drop=true, then the code makes use of oboe.drop, and it should successfully parse the whole response.

About

Trying to reproduce a possible memory leak in oboe.js

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published