1198864 - Refreshing Music app while profiling crashes simulator / closes app

Status: RESOLVED INVALID

(DevTools :: Performance Tools (Profiler/Timeline), defect, P3)

Description

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

STR:

1. Install a 2.5 simulator build
  * Need to use Nightly
  * Disable add-on signing (xpinstall.signatures.required)
  * Note: For Mac, I had to go to the directory, then click on the file link, instead of just pasting the URL
  * Mac: https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central/fxos-simulator-2.5-mac64.xpi
  * Windows: https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central/fxos-simulator-2.5-win32.xpi
  * Linux: https://tools.taskcluster.net/index/artifacts/#gecko.v1.mozilla-central.latest.linux.b2g-desktop/gecko.v1.mozilla-central.latest.linux.b2g-desktop.opt
2. Open WebIDE
3. Start Simulator 2.5 from the runtime menu on the right
4. Select the Music app from the app menu on the left
5. Open toolbox if not already (Wrench icon)
6. Go to performance tab, start profiling
7. Press Cmd+R to refresh the app while profiling

ER:

The app should refresh and profiling continues.  This works for most apps, try the Clock for example.

AR:

The entire simulator crashes.  On a real device, I would expect on the app to close / crash.  (The simulator is single process, devices are multi process.)

Comment 1

[Wilson Page [:wilsonpage]]

Removing the <audio> from the DOM seems to fix this.

Comment 2

[Jordan Santell [:jsantell] [@jsantell]]

(In reply to Wilson Page [:wilsonpage] from comment #1)
> Removing the <audio> from the DOM seems to fix this.

That's even more confusing.

Does anyone know what's crashing? And what would cause <audio> to crash it? Is this a WebIDE, FxOS, DOM or perftools thing?

Comment 3

[Victor Porof [:vporof][:vp]]

Triaging. Filter on ADRENOCORTICOTROPIC (yes).

Comment 4

[Jan Honza Odvarko [:Honza] (always need-info? me)]

This report is related to the old DevTools Profiler.
The Performance panel now points to the new Firefox profiler available at profiler.firefox.com
Closing as Invalid bug