Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
what is in update.zip ? can you share that file to triage this issue
fl...@google.com
da...@google.com
ap...@google.com
MHC19Q for Nexus 5X (bullhead) - https://dl.google.com/dl/android/aosp//bullhead-ota-mhc19q-8fe67a2b.zip
N4F26T for Nexus 5X (bullhead) -https://dl.google.com/dl/android/aosp/bullhead-ota-n4f26t-648ce802.zip
WW-12.2.5.23 for Asus ZenFone Go (ASUS_X014D) -http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZB452KG/UL-ASUS_X014D-WW-12.2.5.23-user.zip
Look like, this happens only with a big images.
N4F26T for Nexus 5X (bullhead) -
WW-12.2.5.23 for Asus ZenFone Go (ASUS_X014D) -
Look like, this happens only with a big images.
[Deleted User] <[Deleted User]>
On Windows 10 (x64)
da...@google.com
related to (and probably worked around for now by) internal bug http://b/36046324
i do think we should also start shipping a 64-bit Windows platform tools package.
we should also consider changing android::base::ReadFdToString to call fstat and pre-size the vector. not worthwhile for reading things like /proc/uptime, but the default expansion behavior for a huge file like a full OTA update is going to result in substantial overhead. (which will explain the regression between .3 and .4, since the former will have allocated exactly the necessary number of bytes.)
lastly (and maybe not worth doing at all, depending on how soon we can get folks to use a 64-bit platform tools on Windows, since all the other platforms are already 64-bit-only), we could consider rewriting the adb sideload code to (a) mmap/munmap rather than actually read in to physical memory or (b) pread. i'm not sure what the performance impact of pread would be (especially on Windows where there is no pread equivalent).
i do think we should also start shipping a 64-bit Windows platform tools package.
we should also consider changing android::base::ReadFdToString to call fstat and pre-size the vector. not worthwhile for reading things like /proc/uptime, but the default expansion behavior for a huge file like a full OTA update is going to result in substantial overhead. (which will explain the regression between .3 and .4, since the former will have allocated exactly the necessary number of bytes.)
lastly (and maybe not worth doing at all, depending on how soon we can get folks to use a 64-bit platform tools on Windows, since all the other platforms are already 64-bit-only), we could consider rewriting the adb sideload code to (a) mmap/munmap rather than actually read in to physical memory or (b) pread. i'm not sure what the performance impact of pread would be (especially on Windows where there is no pread equivalent).
ma...@marcardar.com
Correction to #5: Windows does support pread() - it's in ReadFile()'s OVERLAPPED parameter.
je...@gmail.com
@7: we'd still need to write the pread wrapper, though. (similar if we went with mmap/munmap.)
https://android-review.googlesource.com/#/c/355481/ pre-sizes the vector, which should be enough to undo the regression from '.3 to '.4...
da...@google.com
[Deleted User] <[Deleted User]>
Hi I'm getting the same issue on Windows 10 when I try to sideload a TWRP backup.
- adb devices gives my device
- adb usb gives error: closed
- adb sideload 6.13.771.4_ckpv5.zip gives
loading: '6.13.771.4_ckpv5.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Please can somebody help with this issue I've been trying to sort this for 3 days. Thanks.
- adb devices gives my device
- adb usb gives error: closed
- adb sideload 6.13.771.4_ckpv5.zip gives
loading: '6.13.771.4_ckpv5.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Please can somebody help with this issue I've been trying to sort this for 3 days. Thanks.
yb...@google.com
I also get this problem. Is there a workaround?
cr...@shou.tv
I also get this error message when trying to update Android OS 7.1.1 from N6F26R to N6F26U security patch for Nexus 6. Please help. Thank you.
da...@google.com
It happens when i try to flash any rom to my OnePlus 3, how can i solve it?
pi...@gmail.com
Trying to sideload via adb on Win10 gives me this as well. Nexus 6 trying to sideload from 7.0 to 7.1.1 (N6F26U, Mar 2017)
ai...@gmail.com
My Nexus 9 is on a bootloop and is locked so this was my way out of the bootloop but I've got the same error std::bad_alloc...
If someone has found a way to suppress this error let us know !
If someone has found a way to suppress this error let us know !
Description
Version used: 1.0.0
Room currently supports RxJava and LiveData, but it would be great to also have support for Kotlin's Coroutines.
In a basic implementation this could be achieved with supporting the following types:
- Query: Deferred<T>
- Insert: Job or Deferred<Long>
- Delete: Job or Deferred<Int>
- Update: Job or Deferred<Int>
What could be really awesome though would be implementing support for the `suspend` keyword, as the developer would be able to write just:
```
@Query("SELECT * FROM ITEMS")
suspend fun getItems(): List<Item>
```
I understand this might be tricky to implement on your side though, since a suspend function has got a continuation parameter and that might be an issue with the way Room currently works.