"Unfortunately, Firefox has stopped." #105

Closed
polyzen opened this Issue Dec 20, 2015 · 36 comments

Comments

Projects
None yet
3 participants
@vanitasvitae

This comment has been minimized.

Show comment Hide comment
@vanitasvitae

vanitasvitae Dec 20, 2015

Same for Orfox.

Same for Orfox.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 20, 2015

Contributor

That's strange. It appears to be the same GeckoLinker issues as before but the workaround is still in place.

Contributor

thestinger commented Dec 20, 2015

That's strange. It appears to be the same GeckoLinker issues as before but the workaround is still in place.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 20, 2015

Contributor

12-20 11:24:25.586 7325 7340 D GeckoLoader: Gecko environment env0: null

Contributor

thestinger commented Dec 20, 2015

12-20 11:24:25.586 7325 7340 D GeckoLoader: Gecko environment env0: null

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 20, 2015

Contributor

Looks like the environment variables aren't being passed along. I can't look into it right now but that's probably the problem (if anyone wants to fiddle with platform_frameworks_base).

Contributor

thestinger commented Dec 20, 2015

Looks like the environment variables aren't being passed along. I can't look into it right now but that's probably the problem (if anyone wants to fiddle with platform_frameworks_base).

@vanitasvitae

This comment has been minimized.

Show comment Hide comment
@vanitasvitae

vanitasvitae Dec 21, 2015

I found that nearly all apps that display html content (All browsers, K9 Mail, apps that use WebView) are not working for me. Has that to do with #96?

PS: I should add, that at least "Browser" worked for a short while after the installation, but now crashes.

I found that nearly all apps that display html content (All browsers, K9 Mail, apps that use WebView) are not working for me. Has that to do with #96?

PS: I should add, that at least "Browser" worked for a short while after the installation, but now crashes.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 21, 2015

Contributor

No, nothing to do with that. I don't know what's wrong and I'm working on it. I think there's more than one issue and the Firefox stuff isn't related.

Contributor

thestinger commented Dec 21, 2015

No, nothing to do with that. I don't know what's wrong and I'm working on it. I think there's more than one issue and the Firefox stuff isn't related.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 21, 2015

Contributor

Issues like this are bottlenecked by build time. Need better hardware to get through this stuff faster. I've been building all day.

Contributor

thestinger commented Dec 21, 2015

Issues like this are bottlenecked by build time. Need better hardware to get through this stuff faster. I've been building all day.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 21, 2015

Contributor

I think I've narrowed down the issue in non-Firefox browsers to the set of recent Bionic commits. I'm not entirely sure yet and it needs to be narrowed down to a specific one. I'm still working on narrowing down the cause of the Firefox issue. Just need to keep reverting / unreverting changes and building again until the cause is known.

Contributor

thestinger commented Dec 21, 2015

I think I've narrowed down the issue in non-Firefox browsers to the set of recent Bionic commits. I'm not entirely sure yet and it needs to be narrowed down to a specific one. I'm still working on narrowing down the cause of the Firefox issue. Just need to keep reverting / unreverting changes and building again until the cause is known.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 21, 2015

Contributor

The Firefox issue is at least narrowed down to either being caused by user builds or the Bionic changes.

Contributor

thestinger commented Dec 21, 2015

The Firefox issue is at least narrowed down to either being caused by user builds or the Bionic changes.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 21, 2015

Contributor

The non-Firefox issues might be fixed in the upcoming release in a few hours. Firefox issues are still there and need to be narrowed down.

Contributor

thestinger commented Dec 21, 2015

The non-Firefox issues might be fixed in the upcoming release in a few hours. Firefox issues are still there and need to be narrowed down.

@polyzen

This comment has been minimized.

Show comment Hide comment
@polyzen

polyzen Dec 21, 2015

@vanitasvitae, K-9 works fine here

@thestinger could there be a bigger issue with permissions than #104? The storage permission for Spotify also had to be manually set.

Edit: vanitasvitae, have you manually enabled any permissions? To match cm, I enabled all but location for Play Services. The Play Store and Google Services permissions already matched.

polyzen commented Dec 21, 2015

@vanitasvitae, K-9 works fine here

@thestinger could there be a bigger issue with permissions than #104? The storage permission for Spotify also had to be manually set.

Edit: vanitasvitae, have you manually enabled any permissions? To match cm, I enabled all but location for Play Services. The Play Store and Google Services permissions already matched.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 21, 2015

Contributor

The storage permission for Spotify also had to be manually set.

Doubt it. CopperheadOS doesn't change any of that. Lots of apps have problems with the dynamic permissions in Android 6.0. The Google Play exceptions are certainly not a bug.

Contributor

thestinger commented Dec 21, 2015

The storage permission for Spotify also had to be manually set.

Doubt it. CopperheadOS doesn't change any of that. Lots of apps have problems with the dynamic permissions in Android 6.0. The Google Play exceptions are certainly not a bug.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 21, 2015

Contributor

I think the Chromium/WebView issue is caused by overly aggressive dynamic fortify changes introduced recently and if that's the case then it's fixed now. The Firefox problem is unrelated and is likely related to the problems from before. It's probably caused by OpenBSD malloc but it's not clear how.

Contributor

thestinger commented Dec 21, 2015

I think the Chromium/WebView issue is caused by overly aggressive dynamic fortify changes introduced recently and if that's the case then it's fixed now. The Firefox problem is unrelated and is likely related to the problems from before. It's probably caused by OpenBSD malloc but it's not clear how.

@vanitasvitae

This comment has been minimized.

Show comment Hide comment
@vanitasvitae

vanitasvitae Dec 21, 2015

@polyzen I changed some permissions, but I changed them back to check, if this causes the crashes. Still crashes. I found that there is a subcategory in the permissions concerning email stuff (reading attachements and so on) and K-9 is disabled in all of these categories. When I switch the on and go a level up and click the permission again, K-9 is disabled again. May that cause K9 to crash?

PS: Also I realized that photos that I take are not saved to memory. This affects Camera as well as Focal. Permissions aren't touched and seem to be right here. Should we open a new Issue for this or is this related?

@polyzen I changed some permissions, but I changed them back to check, if this causes the crashes. Still crashes. I found that there is a subcategory in the permissions concerning email stuff (reading attachements and so on) and K-9 is disabled in all of these categories. When I switch the on and go a level up and click the permission again, K-9 is disabled again. May that cause K9 to crash?

PS: Also I realized that photos that I take are not saved to memory. This affects Camera as well as Focal. Permissions aren't touched and seem to be right here. Should we open a new Issue for this or is this related?

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 22, 2015

Contributor

There's a new release but it's still problematic. I don't need new bug reports just yet. I need to fix the existing problems which is taking quite some time, and those may be the causes of other problems.

Applications crashing due to handling the Android 6.0 dynamic permissions poorly isn't a bug though. It's not a CopperheadOS feature.

Contributor

thestinger commented Dec 22, 2015

There's a new release but it's still problematic. I don't need new bug reports just yet. I need to fix the existing problems which is taking quite some time, and those may be the causes of other problems.

Applications crashing due to handling the Android 6.0 dynamic permissions poorly isn't a bug though. It's not a CopperheadOS feature.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 22, 2015

Contributor

One of the Firefox compatibility issues has been fixed so it now works in userdebug builds. It doesn't yet work in user builds so it won't work with the published releases. It seems like it must be something like a missing SELinux rule.

Contributor

thestinger commented Dec 22, 2015

One of the Firefox compatibility issues has been fixed so it now works in userdebug builds. It doesn't yet work in user builds so it won't work with the published releases. It seems like it must be something like a missing SELinux rule.

@vanitasvitae

This comment has been minimized.

Show comment Hide comment
@vanitasvitae

vanitasvitae Dec 22, 2015

Okay. I appreciate your hard work on this project. Btw, Android IMSI Catcher Detector also crashes with and without PaX-softmode enabled. Didn't want to open a new issue since you said you don't need new bug reports just yet :)

Okay. I appreciate your hard work on this project. Btw, Android IMSI Catcher Detector also crashes with and without PaX-softmode enabled. Didn't want to open a new issue since you said you don't need new bug reports just yet :)

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 22, 2015

Contributor

I think the user build SELinux rules are too strict and it could be the same issue across most of these applications. I've found a few issues with user builds so far but it's important to get it working. It seems that AOSP is only really used for eng and userdebug builds in practice. There are some rough edges to fix.

Contributor

thestinger commented Dec 22, 2015

I think the user build SELinux rules are too strict and it could be the same issue across most of these applications. I've found a few issues with user builds so far but it's important to get it working. It seems that AOSP is only really used for eng and userdebug builds in practice. There are some rough edges to fix.

@vanitasvitae

This comment has been minimized.

Show comment Hide comment
@vanitasvitae

vanitasvitae Dec 22, 2015

Btw: Are there any plans to root the ROM by default (like in the CM-builds?) Tried to do root my device from within, but then I end up in a bootloop :/

Btw: Are there any plans to root the ROM by default (like in the CM-builds?) Tried to do root my device from within, but then I end up in a bootloop :/

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 22, 2015

Contributor

The main release will be unrooted to avoid the attack surface of a root implementation. CyanogenMod's implementation was found to be quite insecure and while the obvious issues are now fixed it is still a liability. There can be an alternative channel with root and more debugging support down the road when the project has more resources.

Contributor

thestinger commented Dec 22, 2015

The main release will be unrooted to avoid the attack surface of a root implementation. CyanogenMod's implementation was found to be quite insecure and while the obvious issues are now fixed it is still a liability. There can be an alternative channel with root and more debugging support down the road when the project has more resources.

@polyzen

This comment has been minimized.

Show comment Hide comment
@polyzen

polyzen Dec 22, 2015

@vanitasvitae, this[] worked for me. Used the update.zip format
[] http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394

On Tue, Dec 22, 2015 at 3:24 PM, vanitasvitae notifications@github.com
wrote:

Btw: Are there any plans to root the ROM by default (like in the
CM-builds?) Tried to do root my device from within, but then I end up in a
bootloop :/


Reply to this email directly or view it on GitHub
#105 (comment)
.

polyzen commented Dec 22, 2015

@vanitasvitae, this[] worked for me. Used the update.zip format
[] http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394

On Tue, Dec 22, 2015 at 3:24 PM, vanitasvitae notifications@github.com
wrote:

Btw: Are there any plans to root the ROM by default (like in the
CM-builds?) Tried to do root my device from within, but then I end up in a
bootloop :/


Reply to this email directly or view it on GitHub
#105 (comment)
.

@vanitasvitae

This comment has been minimized.

Show comment Hide comment
@vanitasvitae

vanitasvitae Dec 22, 2015

@polyzen Nice, it worked for me too. Thanks 👍

@polyzen Nice, it worked for me too. Thanks 👍

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 23, 2015

Contributor

Finally narrowed down the Firefox issue and have a solution that should work. Firefox breaks with the combination of PR_SET_DUMPABLE == 0 (which is the case in user builds) and hidepid=2, but not either alone. It crashes because it doesn't have proper error handling and that makes the problem seem a lot worse than it really turned out to be.

Part A (from earlier): https://github.com/CopperheadOS/kernel_lge_hammerhead/commit/18b4a32dcaf788cceb482b96161045b553e1ae3b (was missing in PaX upstream, going to be fixed there too)
Part B (the remaining issue): https://github.com/CopperheadOS/kernel_lge_hammerhead/commit/5275290bc83b37b33a09080b4fd54f6a8fc6cab7 (a backport to both the 3.4 and 3.10 Android kernels)

Contributor

thestinger commented Dec 23, 2015

Finally narrowed down the Firefox issue and have a solution that should work. Firefox breaks with the combination of PR_SET_DUMPABLE == 0 (which is the case in user builds) and hidepid=2, but not either alone. It crashes because it doesn't have proper error handling and that makes the problem seem a lot worse than it really turned out to be.

Part A (from earlier): https://github.com/CopperheadOS/kernel_lge_hammerhead/commit/18b4a32dcaf788cceb482b96161045b553e1ae3b (was missing in PaX upstream, going to be fixed there too)
Part B (the remaining issue): https://github.com/CopperheadOS/kernel_lge_hammerhead/commit/5275290bc83b37b33a09080b4fd54f6a8fc6cab7 (a backport to both the 3.4 and 3.10 Android kernels)

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 23, 2015

Contributor

Going to be fixed in the next release later today.

Contributor

thestinger commented Dec 23, 2015

Going to be fixed in the next release later today.

@polyzen

This comment has been minimized.

Show comment Hide comment
@polyzen

polyzen Dec 23, 2015

\o/

polyzen commented Dec 23, 2015

\o/

@polyzen

This comment has been minimized.

Show comment Hide comment
@polyzen

polyzen Dec 23, 2015

@vanitasvitae, sorry, did not respond to your earlier message.

I found that there is a subcategory in the permissions concerning email stuff (reading attachements and so on) and K-9 is disabled in all of these categories. When I switch the on and go a level up and click the permission again, K-9 is disabled again. May that cause K9 to crash?

The permissions were the same here; haven't had to change them. It's been functional; can't recall if it's crashed..

PS: Also I realized that photos that I take are not saved to memory. This affects Camera as well as Focal. Permissions aren't touched and seem to be right here. Should we open a new Issue for this or is this related?

Haven't had trouble here, either. I'm on hammerhead-ota_update-2015.12.18.13.08.17.zip

polyzen commented Dec 23, 2015

@vanitasvitae, sorry, did not respond to your earlier message.

I found that there is a subcategory in the permissions concerning email stuff (reading attachements and so on) and K-9 is disabled in all of these categories. When I switch the on and go a level up and click the permission again, K-9 is disabled again. May that cause K9 to crash?

The permissions were the same here; haven't had to change them. It's been functional; can't recall if it's crashed..

PS: Also I realized that photos that I take are not saved to memory. This affects Camera as well as Focal. Permissions aren't touched and seem to be right here. Should we open a new Issue for this or is this related?

Haven't had trouble here, either. I'm on hammerhead-ota_update-2015.12.18.13.08.17.zip

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 24, 2015

Contributor

The new release is uploaded for the Nexus 9 and will be uploaded for the Nexus 5 soon.

Contributor

thestinger commented Dec 24, 2015

The new release is uploaded for the Nexus 9 and will be uploaded for the Nexus 5 soon.

@thestinger thestinger closed this Dec 24, 2015

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 24, 2015

Contributor

The Nexus 5 release is out now.

Contributor

thestinger commented Dec 24, 2015

The Nexus 5 release is out now.

@polyzen

This comment has been minimized.

Show comment Hide comment
@polyzen

polyzen Dec 24, 2015

👍

Note: Updating doesn't keep gapps and su installations intact. You will have to reinstall them directly after updating (before booting). Install opengapps last due to this: opengapps/opengapps#201. Edit: Looks like superuser.zip flashes fine after flashing opengapps.

polyzen commented Dec 24, 2015

👍

Note: Updating doesn't keep gapps and su installations intact. You will have to reinstall them directly after updating (before booting). Install opengapps last due to this: opengapps/opengapps#201. Edit: Looks like superuser.zip flashes fine after flashing opengapps.

@vanitasvitae

This comment has been minimized.

Show comment Hide comment
@vanitasvitae

vanitasvitae Dec 24, 2015

Unfortunately the update 2015.12.23 does not fix this issue for me.
I still cannot take pictures and any app that shows html content crashes :/
I will try 2015.12.24, to see, if the crashes disappear.

Edit: The strange thing is that it worked for me twice right after installing the updates. I don't know what I did then, but a few hours later it crashes again.

Unfortunately the update 2015.12.23 does not fix this issue for me.
I still cannot take pictures and any app that shows html content crashes :/
I will try 2015.12.24, to see, if the crashes disappear.

Edit: The strange thing is that it worked for me twice right after installing the updates. I don't know what I did then, but a few hours later it crashes again.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 24, 2015

Contributor

This bug tracks the Firefox two issues, not the other issues. I haven't done anything about the other issues yet.

Contributor

thestinger commented Dec 24, 2015

This bug tracks the Firefox two issues, not the other issues. I haven't done anything about the other issues yet.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 24, 2015

Contributor

#112 is the next issue that's going to be worked on and it may be what you're running into.

Contributor

thestinger commented Dec 24, 2015

#112 is the next issue that's going to be worked on and it may be what you're running into.

@vanitasvitae

This comment has been minimized.

Show comment Hide comment
@vanitasvitae

vanitasvitae Dec 24, 2015

Ah okay, sorry. Orfox also still crashes on my device (2015-12-23).

Ah okay, sorry. Orfox also still crashes on my device (2015-12-23).

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 24, 2015

Contributor

I'm aware that there are general stability issues but that's not related to the issues here. If it ever works for you, then you aren't running into this (and I know you're not because it's fixed).

Contributor

thestinger commented Dec 24, 2015

I'm aware that there are general stability issues but that's not related to the issues here. If it ever works for you, then you aren't running into this (and I know you're not because it's fixed).

@vanitasvitae

This comment has been minimized.

Show comment Hide comment
@vanitasvitae

vanitasvitae Dec 24, 2015

Okay thank you 👍 Let me know if I can help with logs or something. I'd really like to help in some way.

Okay thank you 👍 Let me know if I can help with logs or something. I'd really like to help in some way.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 24, 2015

Contributor

#112 tracks whatever is causing the inconsistent access errors. I think it's one bug across all the places where it's happening. It's probably an issue with one of the Bionic changes. There were some minor tweaks as part of the port of AOSP and one of those might have been wrong. It needs to be narrowed down by reverting Bionic changes, doing a clean build and then thoroughly testing to see if it fixes the problem. It's very time consuming so that's why it takes a while to fix these issues despite days of work.

Contributor

thestinger commented Dec 24, 2015

#112 tracks whatever is causing the inconsistent access errors. I think it's one bug across all the places where it's happening. It's probably an issue with one of the Bionic changes. There were some minor tweaks as part of the port of AOSP and one of those might have been wrong. It needs to be narrowed down by reverting Bionic changes, doing a clean build and then thoroughly testing to see if it fixes the problem. It's very time consuming so that's why it takes a while to fix these issues despite days of work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment