mootools Request leak test

100%

mootools Request leak test

✓ Published0🌍 Public

Last edited Sep 10, 2012

Created on May 5, 2012

This example demonstrates a memory leak in MooTools' Request class by repeatedly fetching a large JSON file and rendering a world map as a GeoJSON FeatureCollection. The page uses MooTools 1.3.0's `Request` and `setTimeout` to continuously re-request `index.json` every second, with each response containing complex polygon coordinates. The visualization shows how the browser's memory consumption grows over time as the request-response cycle remains active, illustrating the degradation experienced during long-running sessions with large payloads.

AI-generated description

As reported on mootools ML:

gdot 9:42 PM (6 hours ago)

to mootools-users

This leak still exists in 1.3.2 :(

On Thursday, December 23, 2010 1:52:14 PM UTC-5, Luke Ehresman wrote:

I have discovered what I believe to be a pretty serious memory leak in the Request class. My site has long-running scripts with large data payloads. So, a user may leave the page open for days at a time without reloading the page. During that time, the site makes many AJAX requests to my server. I've noticed that my browser (all browsers I've tested -- Chrome, Safari, and Firefox) degrade pretty quickly and consume copious amounts of memory within a few hours.

After several days of debugging, I have identified that it's a problem with the Request class in MooTools. Here is a sample script to recreate the problem:

Similar vizzes

Loading thumbnail…

The issue & showcase

This example demonstrates how MooTools’ getComputedSize() method mishandles non-integer pixel dimensions, causing layout elements to overflow or disappear when a user zooms the browser. Three test cases show progressively larger compensation gaps between two floating divs, revealing accumulated rounding errors from internal toInt() calls. The page renders HTML divs and reports measured values in a live JavaScript report, directly comparing pixel-perfect layouts against zoom-level artifacts. It uses MooTools Core 1.4.4 and standard DOM APIs for size computation and display.

GGerHobbelt

58% match

Loading thumbnail…

d3-timer memory leak

This example demonstrates a memory leak in d3-timer by creating a timer that runs indefinitely with a 150-millisecond delay. The page loads the d3-timer library from a CDN and instantiates a timer via `d3.timer()`, passing an empty callback that executes on each tick. The visualization shows how a timer persists without explicit disposal, highlighting potential performance issues in long-running applications. The code uses plain HTML and JavaScript with no rendering, making the leak’s behavior visible through browser developer tools rather than visual output.

CCurran Kelleher

58% match

Loading thumbnail…

Polymaps / JSONP Queue

This example demonstrates Polymaps loading geographic data asynchronously through a JSONP queue. It shows how the library fetches map tiles from a remote server using a callback-based mechanism, enabling cross-domain requests without CORS. The code extends `po.queue` with a `jsonp` function that injects a script tag, substituting a generated callback ID via the `{C}` placeholder in the URL template. The `Url.js` patch adds support for this placeholder, allowing the queue to manage multiple simultaneous requests while tracking active loads and cleanup procedures.

Mmbostock

56% match

Loading thumbnail…

GeoJSON Experiments

This example displays geographic data on an interactive Mapbox map, using the Mapbox.js library and a full-screen map div. It fetches GeoJSON data from a CouchDB view via a jQuery `$.getJSON` call, then loads the returned feature collection into the map’s `featureLayer` with `setGeoJSON`. The map is initialized with `L.mapbox.map` and centered on coordinates (10.1, 125.6) at zoom level 5, showing how dynamic GeoJSON can be rendered on a tiled basemap.

CCliffordAnderson

54% match

Loading thumbnail…

React Performance Optimization - Episode 45

This interactive visualization combines a world bubble map and a time-series histogram to explore global migrant deaths in 2019. Users brush over the histogram to filter the map, which plots circles sized by the number of dead and missing at each location. The code uses React with `useMemo` for performance, D3 v5 utilities like `geoNaturalEarth1`, `geoPath`, `geoGraticule`, and `scaleSqrt`, and renders via SVG. Data comes from the Missing Migrants Project and world boundaries from World Atlas TopoJSON.

Rroc286

54% match

Loading thumbnail…

Fork of Hello VizHub

This example loads a geospatial dataset from the world-atlas package and logs the parsed TopoJSON to the browser console. The SVG canvas is configured with a 960 by 500 pixel viewport, but no geometry is rendered. The code uses D3 v5’s `json` function to fetch the remote file and displays a static message imported from an ES6 module.

Lleoxramadani

51% match

Loading thumbnail…

45) React Performance Optimization

This interactive visualization combines a bubble map and a time-series histogram to explore missing migrant incidents. The map projects circles scaled by the square root of the total dead and missing, while brushing the histogram filters the map's displayed data. The code uses React with d3's `geoNaturalEarth1` projection, `geoPath`, and `geoGraticule` for the map, and `scaleSqrt`, `scaleTime`, `bin`, and `brushX` for the histogram. Data is loaded via d3's `csv` function.

Llefat92

51% match

Loading thumbnail…

Gist 2d272134b57b02eb8cdd0c5904249591

This example tests the archival fidelity of a web page by loading a series of images and scripts that mimic dynamic behavior, including DOM manipulation, AJAX requests, and delayed updates. It uses JavaScript’s `XMLHttpRequest` to fetch remote images and replaces them via base64 data URLs, while `setTimeout` and scroll events trigger asynchronous content changes. The page is rendered within an iframe by the pywb web archiving tool, with a banner and rewrite layer applied. The visualization demonstrates how archived sites handle live interactions and resource loading over time.

NN0taN3rd

51% match