StarBurnX occasionally emits AccessViolationExceptions, like the following:
Code:
System.AccessViolationException: Attempted to read or write
protected memory. This is often an indication that other
memory is corrupt.
at RocketDivision.StarBurnX.DriveClass.get_State()
at CDBurnerXP.Forms.CheckDisc.GetDiscDescription()
...
Code:
System.AccessViolationException: Attempted to read or write
protected memory. This is often an indication that other
memory is corrupt.
at RocketDivision.StarBurnX.DriveClass.UnlockTray()
at CDBurnerXP.Forms.BurningBaseForm.ResetUiAfterWork()
...
Code:
System.AccessViolationException: Intento de leer o escribir
en la memoria protegida. A menudo, esto indica que hay otra
memoria da?ada.
en RocketDivision.StarBurnX.DriveClass.Eject()
en
CDBurnerXP_Pro.frmAudioCompilation.mnuEject_Click(Object
sender, EventArgs e)
Code:
System.AccessViolationException: Attempted to read or write
protected memory. This is often an indication that other
memory is corrupt.
at RocketDivision.StarBurnX.DiscInfoClass.Refresh()
at CDBurnerXP.Forms.CheckDisc.RefreshDisc()
How should I handle those? A failed "unlock tray" could be ignored in general, but AccessViolationExceptions usually hint at much deeper problems that can cause the whole application to get unstable.