kilianc/rtail

Aw, Snap!

Open

#73 opened on Jul 13, 2015

View on GitHub
 (9 comments) (0 reactions) (0 assignees)CSS (1,624 stars) (111 forks)batch import
bughelp wantedwebapp

Description

Hey,

Our system administrator recently set-up rtail to output apache access logs across all of our servers. Needless to say, we got a lot of log lines. Consequently leaving rtail open in a tab will eventually produce the "Aw, Snap!" chrome error (http://www.wintips.org/wp-content/uploads/2014/02/Aw-Snap-chrome-error.jpg). Presumably there's some data structure that continues to grow until the error is produced.

Contributor guide

Tech stack
javascriptnodejs
Domain
full stack
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Node.jsChrome DevToolsMemory profiling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the data structures used in rtail's web interface that hold log lines. Look for any unbounded arrays or objects that accumulate over time. Use Chrome's heap profiler to identify growing objects. Check the WebSocket message handling for potential memory leaks. Consider implementing a fixed size buffer or pagination to limit memory usage.