Viewing changelogs in OTA manager crashes (probably WebView) #218

Closed
vanitasvitae opened this Issue Mar 28, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@vanitasvitae

Hi!
When I click an update in the OTA manager to view the changelog, CyanogenModUpdater crashes (probably due to the webview bug). Enabling PaX-Softmode prevents crashes.
Logcat
Im currently on 2016.03.21. Will update now.

Btw: congratulations to your collaborations with FDroid and the guardianproject 👍

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Mar 28, 2016

Contributor

This is the same issue as #216. I don't have time to address it right now.

Contributor

thestinger commented Mar 28, 2016

This is the same issue as #216. I don't have time to address it right now.

@thestinger thestinger closed this Mar 28, 2016

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Mar 28, 2016

Contributor

I'm not going to manually add exceptions for each application using the WebView. The options available are:

a) Drop MPROTECT as a feature
b) Automatically mark all apps using the WebView as requiring an MPROTECT exception
c) Fix the WebView to not require an exception when JavaScript isn't used. AFAIK, it worked fine in the past. This is what should happen, but it might require a lot of work.

I'm unwilling to take the first path right now, and I don't like the second option. I don't have time to implement either the second or third option. PaX is only on the Nexus 5, and even if it was applied to the newer other kernels the userspace features wouldn't be available yet.

Contributor

thestinger commented Mar 28, 2016

I'm not going to manually add exceptions for each application using the WebView. The options available are:

a) Drop MPROTECT as a feature
b) Automatically mark all apps using the WebView as requiring an MPROTECT exception
c) Fix the WebView to not require an exception when JavaScript isn't used. AFAIK, it worked fine in the past. This is what should happen, but it might require a lot of work.

I'm unwilling to take the first path right now, and I don't like the second option. I don't have time to implement either the second or third option. PaX is only on the Nexus 5, and even if it was applied to the newer other kernels the userspace features wouldn't be available yet.

@vanitasvitae

This comment has been minimized.

Show comment Hide comment
@vanitasvitae

vanitasvitae Mar 28, 2016

Okay. I just wanted to notice you about this.
I wish I could help in another way than only submitting bug reports.

Should I stop submitting bug reports having to do with #216 then?

Okay. I just wanted to notice you about this.
I wish I could help in another way than only submitting bug reports.

Should I stop submitting bug reports having to do with #216 then?

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Mar 28, 2016

Contributor

If the traceback just has the WebView 0x8 segmentation fault and is solved by enabling soft mode, then you don't need to report it. If it's something else, I do want to know.

Contributor

thestinger commented Mar 28, 2016

If the traceback just has the WebView 0x8 segmentation fault and is solved by enabling soft mode, then you don't need to report it. If it's something else, I do want to know.

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