Bug 180014 - Memory leak
Summary: Memory leak
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: iPhone / iPad iOS 11
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-25 14:28 PST by atticus
Modified: 2018-02-03 17:24 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description atticus 2017-11-25 14:28:04 PST 
As of iOS 11, these memory leaks began surfacing in our kiosk iPad application (a tablet app that runs 24/7).

Crashes have been found on the following:
- JSC::Heap::runNotRunningPhase(JSC::GCConductor) 
  http://crashes.to/s/b9212ed75c4
- JSC::Heap::runCurrentPhase(JSC::GCConductor, JSC::CurrentThreadState*)
  http://crashes.to/s/23cd9a6ab40
- JSC::Heap::finishChangingPhase(JSC::GCConductor)
  http://crashes.to/s/3abc177f424

This was originally reported in the React Native project https://github.com/facebook/react-native/issues/16843
Comment 1 Alexey Proskuryakov 2017-11-26 07:58:21 PST 
Could you please provide a reproducible test case, or at least leaks tool results from Instruments? 

It’s not clear why you are saying that these crashes are in some way related to memory leaks, so it may be best to file a separate detailed report for each of the crashes. At the very least, we’ll need full crash logs, but chances are that repro cases will be necessary.