-
Notifications
You must be signed in to change notification settings - Fork 4k
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
JNI Error on Scene Transition #831
Comments
This is also posted on StackOverflow: http://stackoverflow.com/q/27769408/132047 |
That is true, after posting in stackoverflow i went over the entire stacktrace to find something interesting things, and found That the error involves picasso. should i delete the question from there or from here? |
It's fine that it is in both places. I'm just trying to avoid a split-brain problem. |
I had similar issue with sharedElementTransition from Fragment A in Activity A to Activity B, some of transitions (like 25%) were failing with similar error. I think the problem is in excessive overdraw (you have a pretty long fragment that is being re-drawed with every transition). Layer exceeds max. dimensions supported by the GPU (1080x10739, max=4096x4096) |
Seems like this was answered on the SO question and we plan on preventing you from exceeding the max texture size with #754 |
I have 2 activities:
ActivityA
,ActivityB
with associated frgments:FragmentA
,FragmentB
respectively.ImageView v
is shared between those two fragments.some Code: ActivityA
ActivityB
FragmentB
4 out of 5 times it's working. but when it's not working i'm getting the Very informative error:
With a very long and even less informative stack trace that i will attach on demand. but interesting part is with Picasso:
Call to
Picasso
Few things that can cause this:
FragmentB
mView
position is calculated dynamically usingViewTreeObserver.OnGlobalLayoutListener
mView
extendsImageView
in order to create Oval effect in both of the Fragments.one last thing: the
Theme
of both of the activities is a child ofstacktrace:
The text was updated successfully, but these errors were encountered: