1197257 - App crashes when profiling page reload performance with WebIDE

Status: RESOLVED FIXED

(Core :: Gecko Profiler, defect)

Description

[Oleg Zasypkin [:azasypkin]]

App doesn't crash when profiling with WebIDE on Fx Desktop Aurora 42.0a2 (2015-08-20), but always crashes with  Fx Desktop Nightly 43.0a1 (2015-08-21), Ubuntu. Flame build is 20150820150207, PVT mozilla-central.

STR:
* Attach WebIDE to gaia Messages app;
* Go to performance tab and press "Start Recording Performance";
* Switch to Console tab and execute "window.location.reload()" there.

Expected result: app that is being profiled shouldn't crash.

Actual result: app always crashes.

Comment 1

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

Hello Oleg, thanks for the report!

Do you have a backtrace? Can you go to about:crashes and paste a link to the most recent entry there in here.

Thanks!

Comment 2

[Oleg Zasypkin [:azasypkin]]

Attachment: logs.zip

(In reply to Nick Fitzgerald [:fitzgen][:nf] from comment #1)
> Hello Oleg, thanks for the report!
> 
> Do you have a backtrace? Can you go to about:crashes and paste a link to the
> most recent entry there in here.
> 
> Thanks!

Hey Nick,

Unfortunately I don't see anything at all at about:crashes (+ System app doesn't ask me to submit crash report), but I'm attaching firefox log and logcat from the device.

Let me know if you need anything else.

Thanks!

Comment 3

[Oleg Zasypkin [:azasypkin]]

Okay, it seems there is something wrong with my existing profile, it works fine if I create a new profile.

Please, tell me if I can help to find out what it's going with my old profile otherwise I think bug can be closed.

Comment 4

[Oleg Zasypkin [:azasypkin]]

Sorry, I was too quick to comment :) My old profile just had enabled "Record Allocations" options, while it's disabled in a new profile by default.

So app crashes only with "Record Allocations" with both my profiles (Fx Dev Edition seems doesn't have such option).

Comment 5

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

Is it the debugging-browser that is crashing or the debuggee-fxos? If fxos, I suspect this is bug 1192401 which has since been fixed on beta, dev-edition, and nightly. I don't know how uplifts for b2g work though.

Comment 6

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

(In reply to Nick Fitzgerald [:fitzgen][:nf] from comment #5)
> Is it the debugging-browser that is crashing or the debuggee-fxos? If fxos,
> I suspect this is bug 1192401 which has since been fixed on beta,
> dev-edition, and nightly. I don't know how uplifts for b2g work though.

You can refer to the "underlying Gecko version" in the B2G landing[1] table.  If it's in current beta, that's back to Gecko 41.  The active B2G under development (2.5) targets branching at Gecko 44, and the previous release (2.2) targets Gecko 37.  So, the bug is fixed for 2.5 only (and I am guessing the previous revision does not contain the bug / feature to begin with).

Your fix should be included in the reporter's B2G build, assuming it landed in m-c before 20150820150207 (their build ID from comment 0).

[1]: https://wiki.mozilla.org/Release_Management/B2G_Landing

Comment 7

[Oleg Zasypkin [:azasypkin]]

(In reply to Nick Fitzgerald [:fitzgen][:nf] from comment #5)
> Is it the debugging-browser that is crashing or the debuggee-fxos?

Yep, debuggee-fxos app is the one that crashes.

> Is it the debugging-browser that is crashing or the debuggee-fxos?
> If fxos, I suspect this is bug 1192401 which has since been fixed on beta, 
> dev-edition, and nightly. I don't know how uplifts for b2g work though.

Mmm bug 1192401 is restricted, I can't access the bug page to compare symptoms.

> Your fix should be included in the reporter's B2G build, 
> assuming it landed in m-c before 20150820150207 (their build ID from comment 0).

Mmm, I still see crash on Flame PVT mozilla-central build and latest nightly (downloaded both few hours ago):

B2G Info:
2.5.0.0-prerelease
Build Identifier: 20150823150207
Platform Version: 43.0a1
Git Commit Info: 342c1b93

Fx Desktop Nightly: 43.0a1 (2015-08-24)

Comment 8

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

Any chance you could try a debug build and get a stack trace?

Comment 9

[Oleg Zasypkin [:azasypkin]]

Sure, can I download ready Linux debug build from somewhere?

If not, will try to compile it tomorrow by myself and report results here.

Comment 10

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

(In reply to Oleg Zasypkin [:azasypkin][⏰UTC+1] from comment #9)
> Sure, can I download ready Linux debug build from somewhere?
> 
> If not, will try to compile it tomorrow by myself and report results here.

I believe this should be what you need: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2015-08-24-mozilla-central-debug/firefox-43.0a1.en-US.debug-linux-x86_64.tar.bz2

Comment 11

[Oleg Zasypkin [:azasypkin]]

Thanks, just a quick heads up: I don't see any additional output in Firefox debug build when app (fxos app on b2g device) crashes while profiling.

But it came to my knowledge that there were some very recent regressions that were causing crashes in B2G (like bug 1197183). So I'm waiting for those fixes to reach PVT to check once again, also will will test with older B2G builds.

Comment 12

[Oleg Zasypkin [:azasypkin]]

No luck, it still crashes, I've just extracted crash report from device [1] with the tool [2].

Does it clarify anything? :)

Thanks!

[1] https://crash-stats.mozilla.com/report/index/5cbf100a-c747-42d1-bc0d-b83782150827
[2] https://pypi.python.org/pypi/b2g_util

Comment 13

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

Top frame is psuedo stack related. Moving to the gecko profiler component and CC'ing some people who might know what's up.

Comment 14

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

Seems like Nick has this going to the right place.

Comment 15

[Gerald Squelart (he/him) (not at Mozilla since 2022-09-15)]

No more WebIDE or Gaia. 😢