java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) } in zl$a@5eda151 [133313734]

Fixed

Bug

Status Update

No update yet.

Description

ni...@gmail.com

created issue #1

May 23, 2019 07:24AM

WorkManager 2.1.0-alpha01
I know 2.1.0-alpha02 is out but I cannot test it as I CANNOT reproduce this issue on both alpha01 and 02.

Proguard mappings
------------------
androidx.work.impl.constraints.trackers.NetworkStateTracker -> zl
androidx.work.impl.constraints.trackers.ConstraintTracker -> yl
androidx.work.impl.constraints.controllers.ConstraintController -> pl
androidx.work.impl.constraints.WorkConstraintsTracker -> ml
androidx.work.impl.background.systemalarm.WorkTimer -> gl

Crash report from user
-----------------
APP_VERSION_NAME=228 armeabi-v7a
ANDROID_VERSION=5.0
BRAND=samsung
PHONE_MODEL=SM-N9005
PRODUCT=hltexx
USER_APP_START_DATE=2019-05-22T09:58:13.756+01:00
USER_CRASH_DATE=2019-05-22T19:21:59.888+01:00
STACK_TRACE=java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) } in zl$a@5eda151
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:933)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:5938)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1400)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1195)
Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@220005dc rejected from java.util.concurrent.ScheduledThreadPoolExecutor@ffebca8[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2011)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:793)
at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:298)
at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:503)
at java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:644)
at gl.a(SourceFile:7)
at dl.b(SourceFile:5)
at ml.a(SourceFile:21)
at pl.b(SourceFile:3)
at pl.a(SourceFile:18)
at yl.a(SourceFile:17)
at zl$a.onReceive(SourceFile:4)
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:923)
... 8 more

LOGCAT=--------- beginning of main
05-22 19:21:59.727 D/AndroidRuntime(11913): Shutting down VM
05-22 19:21:59.757 E/ACRA (11913): ACRA caught a RuntimeException for com.nll.asr
05-22 19:21:59.757 E/ACRA (11913): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) } in zl$a@5eda151
05-22 19:21:59.757 E/ACRA (11913): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:933)
05-22 19:21:59.757 E/ACRA (11913): at android.os.Handler.handleCallback(Handler.java:739)
05-22 19:21:59.757 E/ACRA (11913): at android.os.Handler.dispatchMessage(Handler.java:95)
05-22 19:21:59.757 E/ACRA (11913): at android.os.Looper.loop(Looper.java:145)
05-22 19:21:59.757 E/ACRA (11913): at android.app.ActivityThread.main(ActivityThread.java:5938)
05-22 19:21:59.757 E/ACRA (11913): at java.lang.reflect.Method.invoke(Native Method)
05-22 19:21:59.757 E/ACRA (11913): at java.lang.reflect.Method.invoke(Method.java:372)
05-22 19:21:59.757 E/ACRA (11913): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1400)
05-22 19:21:59.757 E/ACRA (11913): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1195)
05-22 19:21:59.757 E/ACRA (11913): Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@220005dc rejected from java.util.concurrent.ScheduledThreadPoolExecutor@ffebca8[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
05-22 19:21:59.757 E/ACRA (11913): at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2011)
05-22 19:21:59.757 E/ACRA (11913): at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:793)
05-22 19:21:59.757 E/ACRA (11913): at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:298)
05-22 19:21:59.757 E/ACRA (11913): at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:503)
05-22 19:21:59.757 E/ACRA (11913): at java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:644)
05-22 19:21:59.757 E/ACRA (11913): at gl.a(SourceFile:7)
05-22 19:21:59.757 E/ACRA (11913): at dl.b(SourceFile:5)
05-22 19:21:59.757 E/ACRA (11913): at ml.a(SourceFile:21)
05-22 19:21:59.757 E/ACRA (11913): at pl.b(SourceFile:3)
05-22 19:21:59.757 E/ACRA (11913): at pl.a(SourceFile:18)
05-22 19:21:59.757 E/ACRA (11913): at yl.a(SourceFile:17)
05-22 19:21:59.757 E/ACRA (11913): at zl$a.onReceive(SourceFile:4)
05-22 19:21:59.757 E/ACRA (11913): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:923)
05-22 19:21:59.757 E/ACRA (11913): ... 8 more

REPORT_ID=a476ba1d-9c82-4b7a-90cd-5d91e77df69d
IS_SILENT=false

Comments

li...@gmail.com <li...@gmail.com> #2May 23, 2019 10:50AM

Last Action:
2022-01-19 11:01:47,579 [ 43614] INFO - manager.EmulatorProcessHandler - Emulator: /home/ghost/Android/Sdk/emulator/emulator -netdelay none -netspeed full -avd Pixel_API_31
2022-01-19 11:01:47,600 [ 43635] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
2022-01-19 11:01:47,698 [ 43733] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | cannot add library /home/ghost/Android/Sdk/emulator/qemu/linux-x86_64/lib64/vulkan/libvulkan.so: failed
2022-01-19 11:01:47,760 [ 43795] INFO - manager.EmulatorProcessHandler - Emulator: qemu-system-x86_64: -chardev socket,port=45697,host=::1,nowait,nodelay,ipv6,id=modem: address resolution failed for ::1:45697: Name or service not known
2022-01-19 11:02:27,813 [ 83848] INFO - rationStore.ComponentStoreImpl - Saving Project(name=armino_rents, containerState=COMPONENT_CREATED, componentStore=/home/ghost/StudioProjects/armino_rents)KotlinCommonCompilerArguments

ra...@google.com <ra...@google.com> #3May 23, 2019 05:06PM

please run emulator with the following options and post the output here, thanks!
/path/to/emulator -verbose -show-kernel -avd <avename> -feature -ModemSimulator

the above command line will not use modem, just to see if it is related.

ra...@google.com <ra...@google.com> #4May 23, 2019 05:17PM

Yes,it worked.

Attaching the log below.

ni...@gmail.com <ni...@gmail.com> #5May 23, 2019 05:17PM

I'm getting the same error on my Ryzen 1800X on OpenSUSE Tumbleweed:

"qemu-system-x86_64: -chardev socket,port=38379,host=::1,nowait,nodelay,ipv6,id=modem: address resolution failed for ::1:38379: Name or service not known"

Adding the "-feature -ModemSimulator" flags worked around the issue for me.

ra...@google.com <ra...@google.com> #6May 23, 2019 05:20PM

Hi truefalsetrue101@, could you try look at your /etc/hosts file on your machine? On my machine, it looks like

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1	localhost
255.255.255.255	broadcasthost
::1             localhost

If ::1 localhost is missing, that probably explains why "Name or service was not known".

ni...@gmail.com <ni...@gmail.com> #7May 23, 2019 05:31PM

I have that entry. Here's my entire /etc/hosts (my IP and hostname have been replaced with "xxx"):

#
# hosts         This file describes a number of hostname-to-address
#               mappings for the TCP/IP subsystem.  It is mostly
#               used at boot time, when no name servers are running.
#               On small systems, this file can be used instead of a
#               "named" name server.
# Syntax:
#    
# IP-Address  Full-Qualified-Hostname  Short-Hostname
#

127.0.0.1       localhost

# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix
ff02::1         ipv6-allnodes
ff02::2         ipv6-allrouters
ff02::3         ipv6-allhosts
192.168.xxx.xxx xxx

su...@google.com <su...@google.com> #8May 23, 2019 05:51PM

RE#7

bohu@, any idea why this call would fail on host? I am also guessing maybe it has to do with the /etc/resolv.conf on host.

    if ((rc = getaddrinfo(addr, port, &ai, &local)) != 0) {
        error_setg(errp, "address resolution failed for %s:%s: %s", addr, port,
                   gai_strerror(rc));
        goto err;
    }

ni...@gmail.com <ni...@gmail.com> #9May 23, 2019 05:57PM

"I'm getting the same error on my Ryzen 1800X on OpenSUSE Tumbleweed"

could be related to the linux flavor regarding address resolution.
my machine has almost the same config, and the getaddrinfo just works.
I wonder if there is some sys log you can put up here regarding that error.

su...@google.com <su...@google.com> #10May 23, 2019 07:17PM

It seems linux hosts have lots of problem regarding this, might be better use different ways to hook up the modem.

ni...@gmail.com <ni...@gmail.com> #11May 23, 2019 08:03PM

OpenSUSE Tumbleweed has a toggle in it's network settings for "Enable IPv6". I don't have IPv6 on my internet connection and none of my local devices need it, so I usually leave it disabled.

I tried enabling it and viola, the emulator is starting for me again (without needing the ModemSimulator flag).

It looks like that toggle adds net.ipv6.conf.all.disable_ipv6 = 1 to /etc/sysctl.conf.

ra...@google.com <ra...@google.com> #12May 23, 2019 08:21PM

Thanks #11
that is very helpful information.

I was surprised that emulator does not even try ipv4 when ipv6 failed;

error_setg should be just a warning instead of quitting.

ni...@gmail.com <ni...@gmail.com> #13May 23, 2019 08:33PM

"I tried enabling it and viola, the emulator is starting for me again (without needing the ModemSimulator flag)".

Yes,turning IPv6 on worked for me too.

ni...@gmail.com <ni...@gmail.com> #14May 23, 2019 08:33PM

bohu@, shall we close this bug?

ra...@google.com <ra...@google.com> #15May 23, 2019 08:36PM

is this bug closed? I have followed steps in this issue tracker. Only way I can start my emulator is via the command terminal.

ra...@google.com <ra...@google.com> #16May 23, 2019 10:40PM

@bohu It is probably a good idea to make sure that emulator keeps going when the name service resolution fails in ipv6 for at line

if ((rc = getaddrinfo(addr, port, &ai, &local)) != 0) {
        error_setg(errp, "address resolution failed for %s:%s: %s", addr, port,
                   gai_strerror(rc));
        goto err;
    }

li...@gmail.com <li...@gmail.com> #17May 24, 2019 06:13AM

agreed,

there should ahve been more attempts before erroing out

ra...@google.com <ra...@google.com> #18May 24, 2019 03:32PM

Hi, would it be possible to test this bug with the new build on Linux? Thanks! It works on my Linux machine.

li...@gmail.com <li...@gmail.com> #19May 25, 2019 12:20AM

The bug is fixed by CL. I will also make sure this CL is cherry-picked to stable release.

ra...@google.com <ra...@google.com> #20May 29, 2019 04:49AM

Marked as fixed, reassigned to ra...@google.com.

This bug has been verified as fixed with the latest Emulator Stable 32.1.13-10086546 on my Linux workstation. Following steps are followed to reproduce and verify the issue

Disabled Network connectivity on my machine
Launch API 30/31/32 AVDs using older Emulator[API 30 worked and 31/32 failed]
Installed Latest Emulator 32.1.13-10086546
Launch API 30/31/32 AVDs using new Emulator[API 30/31/32 works]