View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0007364 | Valley 1 | Bug - Other | Apr 30, 2012 7:42 am | Apr 30, 2012 8:14 am | |
| Reporter | Steffe | Assigned To | Chris_McElligottPark | ||
| Status | closed | Resolution | not fixable | ||
| Product Version | 1.006 | ||||
| Summary | 0007364: Output_log.txt massive bloat | ||||
| Description | Not sure what causes it, only found one reference to it on the forums. But it seems like the output_log.txt is bloating up pretty badly. So far it's a bit over 100MB, mostly containing the lines: "(Filename: C:/BuildAgent/work/6bc5f79e0a4296d6/Runtime/Misc/Player.cpp Line: 1571) Skipped rendering frame because GfxDevice is in invalid state (device lost)" With 700k+ occurrences so far. | ||||
| Tags | No tags attached. | ||||
| Internal Weight | New | ||||
|
|
Yep, this is an unavoidable thing that the unity 3d engine does when you are alt-tabbed out of the game while it is in fullscreen mode. If you're going to leave the game running in a minimized state for hours and hours, it's best to restart the game when you get back to then reset this file to a smaller state as well as prevent any related out of memory crashes. I wish it wasn't so -- this is just a foible of the underlying engine the game runs on, however. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Apr 30, 2012 7:42 am | Steffe | New Issue | |
| Apr 30, 2012 8:14 am | Chris_McElligottPark | Internal Weight | => New |
| Apr 30, 2012 8:14 am | Chris_McElligottPark | Note Added: 0023056 | |
| Apr 30, 2012 8:14 am | Chris_McElligottPark | Status | new => closed |
| Apr 30, 2012 8:14 am | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Apr 30, 2012 8:14 am | Chris_McElligottPark | Resolution | open => not fixable |
