The "catching up on tile delete queue" doesn't justify an ALERT message.
It happens regularly during normal operation (ufo!) and only informs about unfortunate, but known and deliberate behavior. The user can't do anything about it, anyway. And finally: flooding the console with this message does only *add* to fgfs' sluggish performance and makes every other message go unnoticed.
This commit is contained in:
parent
e59d38bf00
commit
61b5efb772
1 changed files with 2 additions and 2 deletions
|
@ -359,8 +359,8 @@ void FGTileMgr::update_queues()
|
||||||
// get real serious and agressively free up some tiles so
|
// get real serious and agressively free up some tiles so
|
||||||
// we don't explode our memory usage.
|
// we don't explode our memory usage.
|
||||||
|
|
||||||
SG_LOG( SG_TERRAIN, SG_ALERT,
|
SG_LOG( SG_TERRAIN, SG_WARN,
|
||||||
"Alert: catching up on tile delete queue" );
|
"Warning: catching up on tile delete queue" );
|
||||||
}
|
}
|
||||||
|
|
||||||
FGTileEntry* e = delete_queue.front();
|
FGTileEntry* e = delete_queue.front();
|
||||||
|
|
Loading…
Reference in a new issue