Jump to content

Assertion failed: "m_cycles >= 0"


fabio
 Share

Recommended Posts

hrm, I'm torn between wanting to detect problems and avoid annoying messages.

A negative elapsed time can happen on multi-core systems if the timers diverge

(but there was a hotfix from AMD at least to prevent that) and we're switched

from one core to the other.

However, if it happens regularly, then something is awry. If that's the first

time you see it (and it certainly is the first time I see such a report), it

would probably be better to keep the warning in; otherwise, we could remove it.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...