ClassNotFoundException when unmarshalling SavedState [37133281]

Infeasible

Bug

[AOSP] assigned

NeedsInfo

Status Update

No update yet.

Description

wo...@gmail.com

created issue #1

Jan 18, 2017 06:32PM

This ticket is a duplicate (sorry for doing this on purpose) of

https://code.google.com/p/android/issues/detail?id=196430.

The referenced issue is closed because the bug was fixed in an older release. However the bug reappears in the support library 25.x again and there are a lot of comments that are asking for opening the ticket.

But apparently no maintainer is reading closed tickets so I'm opening this to pull the attention there.

Comments

ar...@google.com <ar...@google.com> #2Jan 19, 2017 08:51AM

Assigned to ar...@google.com.

Thank you for the report. We will try to fix this soon. In the meantime, could you please start the emulator from the console (see the commands below), open the camera app to crash it and attach the output, it might help to figure out what the problem is:

cd /Users/YOUR_USERNAME/Library/Android/sdk/emulator
./emulator -list-avds
./emulator -verbose -avd YOUR_AVD_FROM_PREVIOUS_STEP

if there is a crash report to send, please send it and attach the report id.

wo...@gmail.com <wo...@gmail.com> #3Jan 19, 2017 08:54AM

We got a crash report (thanks JP): 872e3b20bc34905b. It says EXC_BAD_INSTRUCTION / 0x00000001 and the console also says "Illegal hardware instruction". I suspect the new MacOS brought a new hypervizor which causes this behavior. Haitao, could you please take a look?

ar...@google.com <ar...@google.com> #4Jan 31, 2017 06:43AM

We have quite some crashes like this:

product_name="AndroidEmulator" AND crash.Reason="EXC_BAD_INSTRUCTION / 0x00000001" AND cpu.Architecture="arm64"

ar...@google.com <ar...@google.com> #5Feb 6, 2017 10:40AM

The most of crashes happen here:

vVertical_Scale_ARGB_8888_Accelerate
vImageVerticalShear_ARGB8888
vImageVerticalShear_ARGB8888
vImageScale_ARGB8888

vRotateClockwise270Degree_ARGB8888_Accelerate2
vRotate_90_ARGB_8888_270Degree_Accelerate2

ha...@gmail.com <ha...@gmail.com> #6Feb 6, 2017 02:29PM

I suspect EXC_BAD_INSTRUCTION happens in vImageRotate90_ARGB8888 and vImageScale_ARGB8888 which are used by webcam on MacOS.

ar...@gmail.com <ar...@gmail.com> #7Feb 6, 2017 04:28PM

With complete honesty, I have to say that I’m extremely disappointed by the handling of this issue by google and by the fact that it came out in the first place. I need to use android studio for work purposes and I am forced to switch to a different machine. Mac OS Sonoma has been in beta testing for months and google has had plenty of time to ensure the application would be properly running. I expect this issue to have the maximum priority and to be solved very soon.

kv...@gmail.com <kv...@gmail.com> #8Feb 7, 2017 03:31PM

Hi rforzani22, I am sorry for this experience. This bug is my top priority. We expect a fix to be merged within a week. You should be able to download a build directly from our build server (https://ci.android.com/builds/branches/aosp-emu-master-dev/grid) once the fix is merged. The release process will take some additional time.

deleted

Restricted

0 B

ha...@gmail.com <ha...@gmail.com> #9Feb 7, 2017 03:41PM

Thanks for making it a top priority, looking forward for the fix, good luck!

[Deleted User] <[Deleted User]> #10Feb 7, 2017 03:51PM

We confirmed #comment6. I removed vImageRotate90... and vImageScale... and use what I could find (which is not as efficient as vImage... ones, we will try to figure out why these functions crash), it does not handle all aspect ratios and resolutions so far (it might crash for different reasons, I will be working on this tomorrow). If anyone wants to try my local build, I can share it.

ar...@google.com <ar...@google.com> #11Feb 8, 2017 10:47AM

I had to downgrade my Mac to Ventura and I realized on Mac Ventura android studio emulator ask for webcam permission which I allowed and worked but on Sonoma it doesn't ask for permission when I open camera app on webcam0

ch...@beyls.net <ch...@beyls.net> #12Feb 21, 2017 06:32PM

I would be willing to try out your local build if you can share it and I’ll let you know my experience.

ch...@beyls.net <ch...@beyls.net> #13Feb 21, 2017 06:39PM

How can I try your local build? Can I download from somewhere?

[Deleted User] <[Deleted User]> #14Mar 16, 2017 04:28PM

rforzani22 and treblew2017, I shared a Google Drive link with you, see your email.

ch...@beyls.net <ch...@beyls.net> #15Mar 17, 2017 07:09PM

Can I try it too?

ar...@google.com <ar...@google.com> #16Jun 13, 2017 04:51AM

lechun.sk, I shared with you.

ar...@google.com <ar...@google.com> #17Jun 19, 2017 06:30AM

Still doesn't work for me It crashes when I open the camera, this report emulator verbose

ch...@beyls.net <ch...@beyls.net> #18Jun 20, 2017 03:02PM

lechun.sk, this is unexpected. Do you mind uploading a crash report and sharing its id?

ch...@google.com <ch...@google.com> #19Jun 28, 2017 09:29AM

redacted

ch...@beyls.net <ch...@beyls.net> #20Jun 28, 2017 11:08AM

lechun.sk, unfortunately a bug report will not help here. It would useful to debug issues inside Android. This crash happens outside. There should be a popup window when you start the emulator asking to send a crash report. Maybe it is not available for local builds. The fix is in code review.

ar...@google.com <ar...@google.com> #21Jul 12, 2017 05:02AM

Status: Won't Fix (Infeasible)

no popup window for asking to send a crash report when I open emulator it again, it freezes like this when open camera