/usr/lib/android-sdk/platform-tools/adb:*** Error in `adb': free(): invalid next size (fast): ADDR ***

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding android-platform-system-core. This problem was most recently seen with package version 1:7.0.0+r33-2, the problem page at https://errors.ubuntu.com/problem/5bb9b8eb97ebbb8b7a67ed05065397f19ffa254d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[hackel (hackel)]

I'm experiencing this issue as well when I run adb on a newly installed Ubuntu 17.10 machine:

$ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
*** Error in `adb': free(): invalid next size (fast): 0x00005636faaac170 ***
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon

[DuckHook (duckhook)]

This affects me on 17.10, but not 16.04.

Exactly same message as hackel's.

[La Pelan (lapelan-r)]

Me too, exactly the same:

$ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
*** Error in `adb': free(): invalid next size (fast): 0x000055e4691271b0 ***
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon

After install Ubuntu Budgie 17.10

[Cefn (6-launchpad-net-cefn-com)]

This persists in 18.04...

cefn@cefn-dell-bionic:~$ adb reboot bootloader
* daemon not running. starting it now on port 5037 *
free(): invalid next size (fast)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon

[Cefn (6-launchpad-net-cefn-com)]

It may be to do with an error in the invocation, as after calling instead with a hyphen...

cefn@cefn-dell-bionic:~$ adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: no devices/emulators found

[Steve Childs (mgsteve)]

Another 'Me Too' here on 17.10. Are there any workarounds for this?

[Tanner Thompson (tbot2112)]

I just got the same error. It went away after I rebooted my machine.

[Eric Fossum (fossum-eric)]

Can confirm a reboot fixed mine as well. Ubuntu 18.04, after installing 'adb'.

[Adam Mackintosh (agm1984)]

+1 confirmed, rebooting fixed it. I noticed that in one of the errors that popped up also. I think it was Android Studio or a system error, but it said 'if problems persist, try rebooting your machine'.

I would recommend, in your terminal:

shutdown -r 0

-r 0 means restart in 0 seconds from now, aka right now.