Aaron Train [:aaronmt] Reporter
	Description • 10 years ago

This bug is for investigating a huge jump in native crash at /dev/ashmem/libmozalloc.so as reported on Google Play affecting mainly Samsung based devices on all channels in Android 4.3 and Android 4.4.

User Comments

  never work after the new update.
  was trying to use clip board to add comment to social feed and crashed
  Does not reliably paste; shuts down arbitrarily.
  I was trying to comment on an article and Firefox stopped when I hit "reply".

Top Devices

  Galaxy S4 (jflte)
  Galaxy Note3 (hlte)
  Galaxy S3 (m0)

	Kevin Brosnan [Ex-Mozilla]
	Comment 3 • 10 years ago

I saw some near hangs using Gmail desktop and Galaxy S3 I9300 mainly in the compose window editing the recipients. Switching to Google keyboard was a bit smoother.

	Aaron Train [:aaronmt] Reporter
	Comment 4 • 10 years ago

(In reply to Aaron Train [:aaronmt] from comment #0)
> 
> Top Devices
> 
>   Galaxy S4 (jflte)

I have this device (I9505XXUGNG8, 4.4.2 KOT49H)

	Aaron Train [:aaronmt] Reporter
	Comment 5 • 10 years ago

Hmm no luck running into any crashes on my S4. Looking at the dashboard now, this has now increased by 143% since last week with an increase in 5,723 reports.

	Richard Newman [:rnewman]
	Comment 6 • 10 years ago

Mark: can we send out a Twitter blast, see if anyone can reliably hit this, and what they're doing to do so?

	Mark Finkle (:mfinkle) (use needinfo?)
	Comment 7 • 10 years ago

(In reply to Richard Newman [:rnewman] from comment #6)
> Mark: can we send out a Twitter blast, see if anyone can reliably hit this,
> and what they're doing to do so?

What would the tweet say? "Does Firefox crash?" I think we need a more focused STR to get useful responses.

	Richard Newman [:rnewman]
	Comment 8 • 10 years ago

Using a Samsung phone or tablet? Did Firefox suddenly start crashing in the last week or two? What are you doing when it crashes? What keyboard do you use?

	Mark Finkle (:mfinkle) (use needinfo?)
	Comment 9 • 10 years ago

Maybe some of Samsung's updates might have caused this? http://samsung-updates.com/

	Dave Miller [:justdave]
	Comment 10 • 10 years ago

I haven't seen any crashes, Verizon Galaxy S4. I use Swype.

	Dave Miller [:justdave]
	Comment 11 • 10 years ago

I also use nightly, not the market version.

	Axel Nennker
	Comment 12 • 10 years ago

My Nexus5, Android 4.4.4, KTU84P crashed repeatedly.
I was reading tweets using the twitter app, then reading gmail and opened a link to the Cordova issues server e.g. https://issues.apache.org/jira/browse/CB-7310 from one email.
Nightly crashed each time I restarted it because the offending page was reloaded at startup.
The crash reporter sent the report and I allowed it to include the page url.
I uninstalled Nightly and reinstalled it the next day.
Today I can not reproduce the crashes.

	Aaron Train [:aaronmt] Reporter
	Comment 13 • 10 years ago

(In reply to Axel Nennker from comment #12)
> My Nexus5, Android 4.4.4, KTU84P crashed repeatedly.
> I was reading tweets using the twitter app, then reading gmail and opened a
> link to the Cordova issues server e.g.
> https://issues.apache.org/jira/browse/CB-7310 from one email.
> Nightly crashed each time I restarted it because the offending page was
> reloaded at startup.
> The crash reporter sent the report and I allowed it to include the page url.
> I uninstalled Nightly and reinstalled it the next day.
> Today I can not reproduce the crashes.

I think in the case here, we're not seeing the crash-reporter for this signature. Regardless, thanks for reporting.

	James Willcox (:snorp) (jwillcox@mozilla.com) (he/him)
	Comment 14 • 10 years ago

I think we might actually be getting crash reports for these, at least for some of them. This one looks similar: https://crash-stats.mozilla.com/report/list?product=FennecAndroid&query_type=contains&range_unit=days&process_type=any&hang_type=any&signature=libmozalloc.so%400xe52&date=2014-09-03+15%3A00%3A00&range_value=28#tab-sigsummary

	Aaron Train [:aaronmt] Reporter
	Comment 15 • 10 years ago

Some of the reports above dip down to API 16 and the devices are scattered with everything

	James Willcox (:snorp) (jwillcox@mozilla.com) (he/him)
	Comment 16 • 10 years ago

Finkle sent me some of the attached logcats on crash-stats, and I found that there were some assertion failures that caused these. I'm thinking this one is too.

	Aaron Train [:aaronmt] Reporter
	Comment 17 • 10 years ago

Anyone have a Moto G?

"Hi, i am using moto g and if i open any link from any note then firefox crashed. Work on it. - Umang"

	Aaron Train [:aaronmt] Reporter
	Comment 18 • 10 years ago

I spent a couple hours yesterday trying to get Firefox to crash on my I9505 (S4) and I couldn't. I did hit many input related hangs though.

	James Willcox (:snorp) (jwillcox@mozilla.com) (he/him)
	Comment 19 • 10 years ago

The crashes here seem similar for 32. They are all assertion failures in IPC (thread_local_posix.cc:33)

https://crash-stats.mozilla.com/report/list?product=FennecAndroid&query_type=contains&range_unit=days&process_type=any&hang_type=any&signature=libmozalloc.so%400xe5a&date=2014-09-09+15%3A00%3A00&range_value=28#tab-reports

	Aaron Train [:aaronmt] Reporter
	Comment 20 • 10 years ago

(In reply to James Willcox (:snorp) (jwillcox@mozilla.com) from comment #19)
> The crashes here seem similar for 32. They are all assertion failures in IPC
> (thread_local_posix.cc:33)
> 
> https://crash-stats.mozilla.com/report/
> list?product=FennecAndroid&query_type=contains&range_unit=days&process_type=a
> ny&hang_type=any&signature=libmozalloc.so%400xe5a&date=2014-09-
> 09+15%3A00%3A00&range_value=28#tab-reports

A couple are xpcom_runtime_abort([4843] ###!!! ABORT: Could not read the system fonts directory: file /home/moz/fennec/gecko/gfx/thebes/gfxFT2FontList.cpp, line 1189), custom roms likely

	Aaron Train [:aaronmt] Reporter
	Comment 21 • 10 years ago

A couple comments yesterday mention opening links from Facebook. Trying both via native & web app.

	[:Cww]
	Comment 22 • 10 years ago

Rob and I looked into this. Distinct spike in crashes was on Aug 22nd on release Firefox but also on Aug 22nd on Beta Firefox per Google play. I'm fairly confident in saying that it's not caused by anything in 32.

Android releases take time to filter out, so if it were caused by that, I'd expect a ramp and not a sudden spike like we're seeing.

I would guess that a website updated, an ad is circulating that crashes us, or a software update in a 3rd party program (including possible malware).

	Sylvestre Ledru [:Sylvestre]
	Comment 23 • 10 years ago

From Sept 20, we can see a huge drop in term of crash (going back to the previous level). cf screenshot

Closing as wontfix?

	Aaron Train [:aaronmt] Reporter
	Comment 24 • 10 years ago

That's really awkward and concerning.

	James Willcox (:snorp) (jwillcox@mozilla.com) (he/him)
	Comment 25 • 10 years ago

So weird. I think we're still going to try to get to the bottom of this.

	Sylvestre Ledru [:Sylvestre]
	Comment 26 • 10 years ago

Anyway, I am going to untrack it. Please resubmit if it appears again.

	BMO Automation
	Comment 27 • 3 years ago

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.