Reply to thread

Message

<blockquote data-quote="bigdude" data-source="post: 210110" data-attributes="member: 57287">I have observed a problem that may be an issue throughout the software. I am under the impression that the log is kept fully in memory based on some recent crashes. I am not certain of the exact cause, but my system has been generating a lot of log entries like this:[Info.][MPMain]: DVDPlayer DVD Warning: 6I looked through the code and found that that event code in dshow.h is a DVD WARNING&nbsp; &nbsp; &nbsp; &nbsp; DVD_WARNING_Read = 6&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; // File Read FailedI am not sure if it is bad media or a strange problem caused by filters or the Firewire changer I use, but on the DVD menu this error is created several times each second. As a result when a DVD finishes and drops back to the menu the log grows continuously and memory consumption does too. Eventually the system starts to thrash and CPU usage jumps to 100% and ths system starts to misbehave. There is nothing else happening on the system so that leads me to the question:Are Logs kept in a dynamically allocated memory buffer that never rolls over ?or that does so based on something other than its size ?This could account for a lot of the mystery freezes I have seen in the forums. Log buffer goes nuts, system freezes...&nbsp; Naturally this is not the original problem, but it is the cause of the freeze and without this the error itself (in this case) is completely harmless since the system manages to ignire it and work.</blockquote>

[QUOTE="bigdude, post: 210110, member: 57287"] I have observed a problem that may be an issue throughout the software. I am under the impression that the log is kept fully in memory based on some recent crashes. I am not certain of the exact cause, but my system has been generating a lot of log entries like this: [Info.][MPMain]: DVDPlayer DVD Warning: 6 I looked through the code and found that that event code in dshow.h is a DVD WARNING DVD_WARNING_Read = 6 // File Read Failed I am not sure if it is bad media or a strange problem caused by filters or the Firewire changer I use, but on the DVD menu this error is created several times each second. As a result when a DVD finishes and drops back to the menu the log grows continuously and memory consumption does too. Eventually the system starts to thrash and CPU usage jumps to 100% and ths system starts to misbehave. There is nothing else happening on the system so that leads me to the question: Are Logs kept in a dynamically allocated memory buffer that never rolls over ? or that does so based on something other than its size ? This could account for a lot of the mystery freezes I have seen in the forums. Log buffer goes nuts, system freezes... Naturally this is not the original problem, but it is the cause of the freeze and without this the error itself (in this case) is completely harmless since the system manages to ignire it and work. [/QUOTE]

Verification