Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashing with java.lang.RuntimeException: Failure from system #10946

Closed
6 tasks done
netizeni opened this issue Apr 4, 2024 · 4 comments
Closed
6 tasks done

Crashing with java.lang.RuntimeException: Failure from system #10946

netizeni opened this issue Apr 4, 2024 · 4 comments
Labels
duplicate Issue or discussion is a duplicate of an existing issue or discussion

Comments

@netizeni
Copy link

netizeni commented Apr 4, 2024

Checklist

  • I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
  • I made sure that there are no existing issues - open or closed - which I could contribute my information to.
  • I have read the FAQ and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected version

v0.26.1

Steps to reproduce the bug

  1. Search for some video
  2. Tap on it
  3. It mostly starts the video with "Sorry, something went wrong." error. Also, comments are randomly shown or not.

I saw two similar issues #10810 and #10748 with no concrete discussion nor a fix, so I'm opening this one.

"Sorry, something went wrong." appears 90% of the time and comments are missing, yet there are video which are opened without the error and comments are loaded.

Expected behavior

Not to get the error and (optionally) see comments.

Actual behavior

It throws an error and randomly shows (or not show) comments.

Screenshots/Screen recordings

No response

Logs

Exception

  • User Action: ui error
  • Request: ACRA report
  • Content Country: US
  • Content Language: en-US
  • App Language: en_US
  • Service: none
  • Version: 0.26.1
  • OS: Linux samsung/o1sxxx/o1s:12/SP1A.210812.016
Crash log

java.lang.RuntimeException: Failure from system
	at android.app.Instrumentation.execStartActivity(Instrumentation.java:1749)
	at android.app.Activity.startActivityForResult(Activity.java:5473)
	at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:712)
	at android.app.Activity.startActivityForResult(Activity.java:5431)
	at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:693)
	at android.app.Activity.startActivity(Activity.java:5817)
	at android.app.Activity.startActivity(Activity.java:5770)
	at org.schabi.newpipe.error.ErrorUtil$Companion.openActivity(ErrorUtil.kt:43)
	at org.schabi.newpipe.error.ErrorUtil$Companion.showSnackbar$lambda$0(ErrorUtil.kt:149)
	at org.schabi.newpipe.error.ErrorUtil$Companion.$r8$lambda$hbVLiP6-HtFc17h3_yyNDsmaIY8(ErrorUtil.kt:0)
	at org.schabi.newpipe.error.ErrorUtil$Companion$$ExternalSyntheticLambda0.onClick(R8$$SyntheticClass:0)
	at com.google.android.material.snackbar.Snackbar.lambda$setAction$0(Snackbar.java:352)
	at com.google.android.material.snackbar.Snackbar.$r8$lambda$4rINiMZz55Dc47hSTCuz-ALWyEw(Snackbar.java:0)
	at com.google.android.material.snackbar.Snackbar$$ExternalSyntheticLambda1.onClick(R8$$SyntheticClass:0)
	at android.view.View.performClick(View.java:7792)
	at android.widget.TextView.performClick(TextView.java:16112)
	at android.view.View.performClickInternal(View.java:7769)
	at android.view.View.access$3800(View.java:910)
	at android.view.View$PerformClick.run(View.java:30218)
	at android.os.Handler.handleCallback(Handler.java:938)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loopOnce(Looper.java:226)
	at android.os.Looper.loop(Looper.java:313)
	at android.app.ActivityThread.main(ActivityThread.java:8751)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)
Caused by: android.os.TransactionTooLargeException: data parcel size 1242008 bytes
	at android.os.BinderProxy.transactNative(Native Method)
	at android.os.BinderProxy.transact(BinderProxy.java:635)
	at android.app.IActivityTaskManager$Stub$Proxy.startActivity(IActivityTaskManager.java:2891)
	at android.app.Instrumentation.execStartActivity(Instrumentation.java:1743)
	... 26 more


Affected Android/Custom ROM version

Android 12

Affected device model

Samsung S21

Additional information

Fresh installation of the latest version of NewPipe with no settings changed.

@netizeni netizeni added bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up labels Apr 4, 2024
@opusforlife2
Copy link
Collaborator

Your crash log doesn't match your given steps. To be very specific, does this crash occur when try to open the error report using the button in the snackbar, or when you simply tap on a video, like you say in step 2?

@opusforlife2 opusforlife2 added the waiting for author If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed. label Apr 5, 2024
@netizeni
Copy link
Author

netizeni commented Apr 5, 2024

When I tap on some video the error appears, but not every time. It loads a video with a slight delay, comments are not shown and the error appears. Lets say in 10 videos, at least 6 or 7 videos show the error.

Also, I'm a long time user of NewPipe, so never had this issue until the latest version.

@github-actions github-actions bot removed the waiting for author If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed. label Apr 5, 2024
@opusforlife2
Copy link
Collaborator

So all you're doing is opening a video and then the app crashes completely? You aren't able to ignore the error and continue using it?

@opusforlife2 opusforlife2 added the waiting for author If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed. label Apr 5, 2024
@netizeni
Copy link
Author

netizeni commented Apr 5, 2024

It doesn't always crash completely, but almost always shows the error.

I'm able to ignore the error, as it appears minimized with "Sorry, something went wrong", but anecdotally, comments are not loaded whenever I'm interested to see them.

@github-actions github-actions bot removed the waiting for author If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed. label Apr 5, 2024
@opusforlife2
Copy link
Collaborator

I'm able to ignore the error

This is what I was looking for. This makes it a duplicate of #10748, which you've linked in your description.

@opusforlife2 opusforlife2 added duplicate Issue or discussion is a duplicate of an existing issue or discussion and removed bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up labels Apr 5, 2024
@netizeni
Copy link
Author

netizeni commented Apr 6, 2024

@opusforlife2 and what happens now, when this issue is closed? That one is opened for three months now with no info will it be fixed, what's causing the issue or any other info beside OP. If there was any, I wouldn't open this one, but continue conversation there.

Based on your comment there, seems like there are more people having it, and it's not something small, considering the complete comment section is not shown.

@opusforlife2
Copy link
Collaborator

There is no conversation to continue. I did what I could in investigating the issue, but I'm not a dev, so the triage work is done as far as I'm concerned. Now it's up to the devs to look at the bug.

Also, this bug is about overly large crash reports. The comments thing is completely unrelated. You can subscribe to the first pinned issue. And in general, make it a habit to look at pinned issues, because they're highlighted for a reason.

@fenopa

This comment was marked as abuse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issue or discussion is a duplicate of an existing issue or discussion
Projects
None yet
Development

No branches or pull requests

3 participants