Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
Issue ID
1285552
Regression
No
[Crash] Unity crashes when no disk space is available with ' dataOffset != file.GetPosition() '
steps to repro
1a. with only 1-2GB of free disk space, open a new 3D template project
1b. import a 16kx16k texture
2. change texture settings on the 16k texture -> uncompressed + 16384 max size
3. click apply after changing texture settings
Expected: unity does not trigger reimport and warns about low disk space
actual: unity starts to reimport (filling remaining disk space by writing to Library and/or Temp folder) then a dialog appears with the only option to quit (and Unity crashes on close)
repro: 2020.1.0b8, 2021.1.0a5
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2021.1):
The crash requires a lot of development work to address - this is currently under consideration.
The workaround is to ensure there is at least 1GB of free disk space when using Unity.
If you are using large assets, more than 1GB of free disk space will be required.
In 2021.1.0a8:
- added a message "this is likely because the disk is full" to the 'fatal error' popup window
- added a new popup warning when there is less than 1GB of free disk space available