ID:114133
 
BYOND Version:484
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Chrome 12.0.742.77
Applies to:Dream Daemon
Status: Unverified

Thus far we've been unable to verify or reproduce this bug. Or, it has been observed but it cannot be triggered with a reliable test case. You can help us out by editing your report or adding a comment with more information.
Descriptive Problem Summary:
BUG: Finished erasure with refcount=7 (ref=5:11) DM (:0)
BUG: Finished erasure with refcount=4 (ref=5:12) DM (:0)
is coming up in the world log, and is corresponding with masssive lag spikes on Hazordhu
Numbered Steps to Reproduce Problem:
Unkown

Expected Results:
No lag
Actual Results:
Lag spikes and bug output
Does the problem occur:
Every time? Or how often?
Unknown
In other games?
unknown
In other user accounts?
Yes
On other computers?
Yes

When does the problem NOT occur?
Earlier BYOND versions
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? No

Workarounds:
Unknown
I've seen reports of this before, but unfortunately you have provided us no information whatsoever that we could use to reproduce the issue. A reliable test case is really important for this one; without that we can't make any headway.
I really have no idea. Along with the update I recently added a new optomized crafting system using DT's Tooltip library. I'll try and get you an exact instance of when this bug occurs and reply here if/when I do.
You need to stop posting duplicate issues on this. I've deleted the other two instead of marking them as duplicates because they have no value whatsoever. I thought the original was an honest mistake but the second one apparently wasn't.
Me? I haven't made any other bug report posts about this except for this one. >_>
If it's being duplicated by more than one person then it's a bug that should be addressed, whether or not the method to reproduce it is included.

If this were just a false claim or a minor glitch then I don't think it would have arisen more than once in the bug reports.
A bug that can't be reproduced usually can't be addressed. But I was specifically referring to the fact that there have been three such bug reports from F0lak.
Lummox JR wrote:
A bug that can't be reproduced usually can't be addressed. But I was specifically referring to the fact that there have been three such bug reports from F0lak.

Like I said, I only posted it once. Perhaps Chrome mucked something up?

Anyways, I'm still trying to find out what this all about. So far I've noticed that refcount 5 doesn't lag, but everything else that's come up has.
Lummox, is there anything you can tell me about the conditions under which this particular BUG message comes up that might be able to help me narrow down the possibilities of the exact cause?