- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yeah, that's a bit of an annoying thing about our log files... To limit our network and disk impact, log lines aren't written to disk immediately, but are buffered in memory first; once that buffer (which is a few kilobytes large, for a handful to a dozen log lines, in general) is full, it's written to disk.
If something causes the FlexEngine.exe instance that is writing to the async log to hang, quite often the last log lines that make it to disk are for one of the actions preceding the culprit...
If you can reproduce the issue during the session (maybe by killing the hanging FlexEngine.exe and performing a UEM refresh), ProcMon might shed some light on the hanging action.