BUG: Bad ref (2:28931) in DecRefCount

ID:1511964
 
Mar 6 2014, 6:23 am
BYOND Version:503
Operating System:Linux
Web Browser:Chrome 33.0.1750.146
Applies to:Dream Seeker
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:
hello to all,I have problems with this report I do not know why this throwing these errors, help me please.
Additionally only about linux in windows these errors are not displayed
//----- log of the game:----
Wed Mar  5 08:38:17 2014
World opened on network port 52900.
Welcome BYOND! (5.0 Public Version 503.1224)
BUG: Bad ref (2:28937) in IncRefCount
BUG: Bad ref (2:28937) in IncRefCount
BUG: Bad ref (2:28937) in DecRefCount
BUG: Bad ref (2:28937) in IncRefCount
BUG: Bad ref (2:28937) in DecRefCount
BUG: Bad ref (2:28937) in DecRefCount
BUG: Bad ref (2:28931) in IncRefCount
BUG: Bad ref (2:28931) in IncRefCount
BUG: Bad ref (2:28931) in DecRefCount
BUG: Bad ref (2:28931) in IncRefCount
BUG: Bad ref (2:28931) in DecRefCount

Numbered Steps to Reproduce Problem:
1-turn on the game in linux
2-after 20 or 30 minutes chashed

Does the problem occur:
Every time? Or how often?
yes Every time,after 20 or 30 minutes of being turned on the server

When does the problem NOT occur?
when turn my game on my pc (windows 7) does not have this type of problem

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
I do not know
Workarounds:
shut down the server: (
Mar 6 2014, 6:56 am
Which 503 is this on? Is it the stable build?

I would actually recommend trying this in 506.1237, first with all threads on; then if that doesn't work, with map threads off, then with all threads off.

Some bugs have been fixed since 503 that could impact this kind of thing.
Mar 6 2014, 8:06 am (Edited on Mar 6 2014, 8:11 am)
In response to Lummox JR
Lummox JR wrote:
Which 503 is this on? Is it the stable build?

I would actually recommend trying this in 506.1237, first with all threads on; then if that doesn't work, with map threads off, then with all threads off.

Some bugs have been fixed since 503 that could impact this kind of thing.

BYOND 5.0 Public (Version 503.1224) on Linux
okey how make all threads off please?
I was using the beta of 506 but my server chashed constantly
Mar 6 2014, 8:33 am
Pass the argument -threads off to DreamMaker, eg

DreamMaker game.dmb 5000 -threads off &
Mar 6 2014, 8:48 am
oHˇ , I'll try immediately Thnaks so much
Mar 6 2014, 6:33 pm
Hello again:
after the updated version of byond the problem persists

[root@Naruteros ~]# DreamDaemon -version
BYOND 5.0 (Version 504.1232) on Linux



Fri Mar  7 08:14:58 2014
World opened on network port 52900.
Welcome BYOND! (5.0 Version 504.1232)
The BYOND hub reports that port 52900 is reachable.
BUG: Bad ref (2:28950) in IncRefCount
BUG: Bad ref (2:28950) in IncRefCount
BUG: Bad ref (2:28950) in DecRefCount
BUG: Bad ref (2:28950) in IncRefCount
BUG: Bad ref (2:28950) in DecRefCount
BUG: Bad ref (2:28950) in DecRefCount
BUG: Bad ref (2:28950) in IncRefCount
BUG: Bad ref (2:28950) in IncRefCount
BUG: Bad ref (2:28950) in DecRefCount
BUG: Bad ref (2:28950) in IncRefCount
BUG: Bad ref (2:28950) in DecRefCount
BUG: Bad ref (2:28950) in DecRefCount
BUG: Bad ref (2:28944) in IncRefCount
BUG: Bad ref (2:28944) in IncRefCount
BUG: Bad ref (2:28944) in DecRefCount
BUG: Bad ref (2:28944) in IncRefCount
BUG: Bad ref (2:28944) in DecRefCount
BUG: Bad ref (2:28944) in DecRefCount
BUG: Bad ref (2:28951) in IncRefCount
BUG: Bad ref (2:28951) in IncRefCount
BUG: Bad ref (2:28951) in DecRefCount
BUG: Bad ref (2:28951) in IncRefCount
BUG: Bad ref (2:28951) in DecRefCount
BUG: Bad ref (2:28951) in DecRefCount

in all cases shows me the same either normal,-threads on,-threads off or -map-threads off
[root@Naruteros bin]# DreamDaemon NaruterosV3.dmb 52900 -trusted  -logself &
[1] 18157

[root@Naruteros bin]# DreamDaemon NaruterosV3.dmb 52900 -trusted -threads on -logself &
[1] 18157

[root@Naruteros bin]# DreamDaemon NaruterosV3.dmb 52900 -trusted -threads off -logself &
[1] 18157

[root@Naruteros bin]# DreamDaemon NaruterosV3.dmb 52900 -trusted  -map-threads off &
[1] 18157
Mar 7 2014, 10:26 am
fIXED
Apparently the error was occurring with this:

world/map_format=TILED_ICON_MAP

turf
    inicio

        nuevo
            MouseEntered()
                usr.AddBrillo()
            MouseExited()
                usr.QuitBrillo()
            Click()
                usr<<'jump.ogg'
                usr.Bienvenida()
                usr.create()

mob/proc
    AddBrillo()
        src.client.screen+=new/obj/NuevoIntro1
        src.client.screen+=new/obj/NuevoIntro2
        src.client.screen+=new/obj/NuevoIntro3
        src.client.screen+=new/obj/NuevoIntro4
        src.client.screen+=new/obj/NuevoIntro5
        src.client.screen+=new/obj/NuevoIntro6

    QuitBrillo()
        for(var/obj/NuevoIntro1/C in usr.client.screen)
            src.client.screen-=C
        for(var/obj/NuevoIntro2/D in usr.client.screen)
            src.client.screen-=D
        for(var/obj/NuevoIntro3/E in usr.client.screen)
            src.client.screen-=E
        for(var/obj/NuevoIntro4/F in usr.client.screen)
            src.client.screen-=F
        for(var/obj/NuevoIntro5/G in usr.client.screen)
            src.client.screen-=G
        for(var/obj/NuevoIntro6/H in usr.client.screen)
            src.client.screen-=H

remove these lines of code and the server goes perfect, thanks so much.
Mar 7 2014, 10:58 am
Interesting. I'll have to see why the objs are having an issue. Looks like I should be able to reproduce that code.
Mar 7 2014, 11:50 am
As another note here, I see that you've mistakenly used usr in the QuitBrillo() proc. usr doesn't belong there. If it had a different value from src for any reason, I could see unpredictable behavior occurring--not that it should cause a bad ref though. I can't help but wonder however if it did contribute in some way.
Mar 7 2014, 11:51 am
Lummox JR changed status to 'Unverified'
Mar 7 2014, 12:41 pm
ok proves to see if that is the problem but I do not think that's it, thanks so much