Fixed
Status Update
No update yet.
Comments
vi...@google.com
vi...@google.com
Can you share emulator version and crash logs.
[Deleted User] <[Deleted User]>
Facing same bug
vi...@google.com
Hi, thanks for the report. Can you describe the problem in more detail? Does this happen every time?
il...@google.com
ap...@google.com
Yes it happens every time whenever I close the emulator after updating to
the latest version of the emulator.
On Fri, Dec 14, 2018 at 5:34 AM <buganizer-system@google.com> wrote:
the latest version of the emulator.
On Fri, Dec 14, 2018 at 5:34 AM <buganizer-system@google.com> wrote:
--
*Sachin Malik*
*Android Developer - Caringforyou IT solutions*
Call: +91 <
sachinmalik413@gmail.com
Please consider the environment before printing this email
il...@google.com
That's quite weird. What system specs do you have? We recently started using mapped files to save guest RAM snapshots. If there is existing corruption on your disk, this might trip issues. Can you try again after running
echo "QuickbootFileBacked = off" >> ~/.android/advancedFeatures.ini
?
echo "QuickbootFileBacked = off" >> ~/.android/advancedFeatures.ini
?
Description
I'm trying to confirm some threading assumptions in a codebase. It currently boils down to the following question:
Can I assume that Fragment.onViewCreated() and Fragment.onResume() are always called on the application's main thread?
As far as I can tell there is no reason for either to be called on a worker thread, but I'm worried my assumption might cause trouble in the future. I'd like to request the addition of "@MainThread" and/or "@AnyThread" to those methods to alleviate that uncertainty.