- Joined
- Oct 12, 2001
- Location
- Los Angeles
OK, first, thankfully this happened just last night and NOT when I was out of town but it very well could have. If any of you have unattended folders, it is very wise to restart them before you leave them, and check the task manager to make sure there isn't something eating up cycles.
Last night when i left my office (yeah I know I work WAY too much) I closed all my apps like I normally do except for EMIII and MBM. When I came in this morning, EMIII said that my frame time for a P541 was like over 8 hours!!! I was like, WTF? Even with optimizations off, frame times would only be like 20mins. I fired up the task manager and saw that ieexplorer was stuck in some sort of loop and taking up 99% of the CPU! Check out my log noting the frame time between 73 and 74:
[04:44:14] Completed 330000 out of 500000 steps (66)
[04:49:59] Writing local files
[04:49:59] Completed 335000 out of 500000 steps (67)
[04:56:02] Writing local files
[04:56:02] Completed 340000 out of 500000 steps (68)
[05:01:50] Writing local files
[05:01:50] Completed 345000 out of 500000 steps (69)
[05:07:35] Writing local files
[05:07:35] Completed 350000 out of 500000 steps (70)
[05:13:22] Writing local files
[05:13:22] Completed 355000 out of 500000 steps (71)
[05:19:12] Writing local files
[05:19:12] Completed 360000 out of 500000 steps (72)
[05:24:59] Writing local files
[05:24:59] Completed 365000 out of 500000 steps (73)
[13:46:03] Writing local files
[13:46:06] Completed 370000 out of 500000 steps (74)
Bottom line is always MAKE SURE it is the core using all your cycles, not some unwanted POS!!!
Last night when i left my office (yeah I know I work WAY too much) I closed all my apps like I normally do except for EMIII and MBM. When I came in this morning, EMIII said that my frame time for a P541 was like over 8 hours!!! I was like, WTF? Even with optimizations off, frame times would only be like 20mins. I fired up the task manager and saw that ieexplorer was stuck in some sort of loop and taking up 99% of the CPU! Check out my log noting the frame time between 73 and 74:
[04:44:14] Completed 330000 out of 500000 steps (66)
[04:49:59] Writing local files
[04:49:59] Completed 335000 out of 500000 steps (67)
[04:56:02] Writing local files
[04:56:02] Completed 340000 out of 500000 steps (68)
[05:01:50] Writing local files
[05:01:50] Completed 345000 out of 500000 steps (69)
[05:07:35] Writing local files
[05:07:35] Completed 350000 out of 500000 steps (70)
[05:13:22] Writing local files
[05:13:22] Completed 355000 out of 500000 steps (71)
[05:19:12] Writing local files
[05:19:12] Completed 360000 out of 500000 steps (72)
[05:24:59] Writing local files
[05:24:59] Completed 365000 out of 500000 steps (73)
[13:46:03] Writing local files
[13:46:06] Completed 370000 out of 500000 steps (74)
Bottom line is always MAKE SURE it is the core using all your cycles, not some unwanted POS!!!