google/closure-compiler

Parser crashes in IDE mode with unclosed regex literal

Open

#2340 opened on Feb 27, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (7,176 stars) (1,197 forks)batch import
Parserhelp wanted

Description

https://closure-compiler-debugger.appspot.com/#input0%3D%2520%2520%252Fwriter.js%253A%26input1%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3D1%26CHECK_SYMBOLS%3D1%26MISSING_PROPERTIES%3D1%26TRANSPILE%3D1%26CHECK_TYPES%3D1%26IDE_MODE%3D1%26CLOSURE_PASS%3D1%26PRESERVE_TYPE_ANNOTATIONS%3D1%26PRETTY_PRINT%3D1

Contributor guide

Tech stack
javajavascript
Domain
toolingdeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 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.
unclear
Prerequisites
JavaScript syntaxJava programmingcompiler internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue provides a link to the Closure Compiler debugger with a specific input that triggers a crash in IDE mode. To investigate, reproduce the crash by loading the provided debugger URL and examining the parser's behavior with unclosed regex literals. Check the parser source code in the repository, particularly files related to regex literal handling (e.g., in the com.google.javascript.rhino package). Look for any recent discussions or commits that might address regex parsing. Since the issue is old with minimal activity, maintainer input may be needed to confirm the expected behavior.