Closed
Description
Steps to Reproduce
- Open Android Studio or VSCode,Make sure the flutter process is running.
- Wait for the hard drive to become full.
- Restart your computer.
- Open the trash.
Logs
null
Screenshot
[✓] Flutter (Channel stable, v1.17.0, on Mac OS X 10.15.4 19E287, locale zh-Hans-CN)
• Flutter version 1.17.0 at /Users/abel/develop/flutter
• Framework revision e6b34c2b5c (8 days ago), 2020-05-02 11:39:18 -0700
• Engine revision 540786dd51
• Dart version 2.8.1
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at /Users/abel/Library/Android/sdk
• Platform android-29, build-tools 29.0.3
• ANDROID_HOME = /Users/abel/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.4.1, Build version 11E503a
• CocoaPods version 1.8.4
[✓] Android Studio (version 3.6)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 44.0.2
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
[!] IntelliJ IDEA Ultimate Edition (version 2019.2.4)
• IntelliJ at /Applications/IntelliJ IDEA.app
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• For information about installing plugins, see
https://flutter.dev/intellij-setup/#installing-the-plugins
[✓] VS Code (version 1.45.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.10.1
[!] Connected device
! No devices available
! Doctor found issues in 2 categories.
Metadata
Metadata
Assignees
Labels
Critical issues such as a build break or regressionAffects or could affect many people, though not necessarily a specific customer.Found to occur in 1.17Occurs in 1.18Building on or for macOS specifically"xcodebuild" on iOS and general Xcode project managementAffects the "flutter" command-line tool. See also t: labels.
Activity
trinicoconutman commentedon May 11, 2020
I am having the same exact problem. I am using the latest flutter and VS Code. It takes about an hour to burn through 100 GB on my MacbookAir 2020.
seekcx commentedon May 11, 2020
I think I may have solved this problem.
Before there was a problem, I used CleanMyMac to clean up some files.
I wonder if some temporary files have been cleaned up, and Flutter cannot create these files properly.
I opened XCode and observed the hard disk space, which was reduced by about 4G, no longer.
Open Android Studio or VSCode again, keep the Flutter process running, and the hard disk space will not continue to decrease.
The problem seems to be solved.
trinicoconutman commentedon May 11, 2020
Hmm, i'm not quite following what the solution was. Did running XCode fix something? Just running VSCode and having the flutter process running seems to be the same process that had the issue before. What changed?
seekcx commentedon May 11, 2020
I don't know the details, but after I run XCode, the problem is indeed solved.
If the problem is not solved, here is another method you can try.
VladyslavBondarenko commentedon May 11, 2020
@trinicoconutman
could you provide your
flutter doctor -v
and investigate what files/directories start to consume so much space?are you experiencing this with any app? with another flutter version?
VladyslavBondarenko commentedon May 11, 2020
@trinicoconutman
consider to file a separate issue with provided info about your case.
@seekcx
I'm going to closed the current one, since it's solved and hardly workable
trinicoconutman commentedon May 11, 2020
Ok, opening XCode worked. Thanks guys.
XinwenCheng commentedon May 13, 2020
I faced this very issue, and problem was temporarily solved after I ran XCode, but once I
flutter run
to iOS device, it happened again.wavecommander commentedon May 13, 2020
I originally posted this on issue #56270, but it was marked off-topic.
I believe this is a more correct spot.
I also experienced my disk being filled up completely by "A Document Being Saved by xcdevice #" files upon attaching an iOS device.
For context, I installed Flutter on macOS 10.14, then upgraded to macOS 10.15, the latest Xcode, and the latest Flutter 1.17 using
flutter upgrade
.Reinstalling Xcode did not fix the problem for me.
I think this was happening because I did not update CocoaPods along with all of the other tools.
Regardless, I played it safe and 'reinstalled' Flutter as well as CocoaPods.
These steps solved my problem:
flutter doctor
(make sure you still have it in your path)sudo gem install cocoapods
pod setup
after CocoaPods finished installingjmagman commentedon May 13, 2020
xcdevice
is the Xcode command line tool Flutter uses to figure out which devices are attached to your host machine. I'm not sure how CocoaPods could be related.I'm guessing the dyld_shared_cache_arm64 are something
xcdevice
is writing to tmp (maybe a copy of ~/Library/Developer/Xcode/iOS\ DeviceSupport/<>/Symbols/System/Library/Caches/com.apple.dyld/dyld_shared_cache_arm64), but the process is getting killed before it can be deleted? Or perhaps it never properly cleans up this file and Flutter is running it so often (every time your app runs) that it's just now noticeable. Seems like Xcode knows how to clean up those files and a launch of Xcode temporarily "fixes" it.wavecommander commentedon May 13, 2020
@jmagman My hunch is that the process cleans up normally, but something is making it crash, leaving these files midway through, and the invoker is simply ignoring the crash, trying again and again in a loop while the device is connected.
I didn't have to run my app for this to occur, the moment I plugged it in, and the plugins and tools etc. are trying to communicate with the device, that is when it started filling my disk.
66 remaining items
pcsosinski commentedon Jun 16, 2020
beta is 1.19.0-4.1.pre, so this is fixed on beta channel
psimondk commentedon Jun 17, 2020
Shoshin23 commentedon Jun 17, 2020
pcsosinski commentedon Jun 17, 2020
@jmagman this looks to require a manual merge into 1.17 (branch: flutter-1.17-candidate.3)
can you take a look at what that merge looks like? seems like most of the conflicts are in tests.
jmagman commentedon Jun 17, 2020
@pcsosinski PR at #59695.
sstadtl commentedon Jun 17, 2020
@Shoshin23
Have you tried opening Xcode => Window => Devices => let the sync finish => reboot ?
that fixed it for me
(and all dev-devices updated to the latest ios version)
psimondk commentedon Jun 17, 2020
jmagman commentedon Jun 17, 2020
This issue was specifically tracking the xcdevice dyld_shared_cache_arm64 generation. There's a PR at #59695 to hotfix to stable.
If you are seeing another issue (related to Android, doctor not finding simctl, whatever), please file it so we can take a look. Locking for now to avoid noise.
pcsosinski commentedon Jun 18, 2020
fixed in 1.17.4