SRL Archive - S.M.A.R.T.

I just ran MSI for less than an hour and when I came back, the SMART window was frozen. As in, it was as if the RS window was a screenshot of where the player was rather than the game itself. I couldn't do anything in game (click tabs, walk, etc.). There was no SMART error, no Simba error, nothing got the Windows "Not Responding" error. I simply closed SMART, and it's working again.

Anyone else have a similar problem?

I've been getting that when running draynor willows - but i get a blackscreen with no explanation

That happens to me, but only if I switch users on my computer then come back to the profile running the script.

Hm, my second run I came back half an hour later, SMART was closed and Simba "wasn't responding", and I had to kill it from the Task Manager.

Anyone know what may cause this? I may just try a fresh install of Simba if it happens again.

Is this with Simba 0.96?

I've experienced the same problem on my friend's computer, I haven't used any scripts in a while on mine.

This has happened to me too.

Again, Simba 0.96?

From: i luffs yeww
Again, Simba 0.96?

Yes, I am using 0.96

From: i luffs yeww
Again, Simba 0.96?

Yes.

Yea

Huh. I'm not sure what was changed so I can't say for sure, but I'll look into it if Wizzup? doesn't figure it out by the time I get out of my meeting tomorrow morning.

One last question.. Was it only MSI? I have no idea how MSI would cause this problem, but I wanted to ask for testing stuff (was gonna run a script that was just in an infinite wait, so I'll see if that causes this problem too).

Any more details would help. ;) (If it happened multiple times at a specific procedure/event/whatever, etc.)

From: i luffs yeww
Huh. I'm not sure what was changed so I can't say for sure, but I'll look into it if Wizzup? doesn't figure it out by the time I get out of my meeting tomorrow morning.

One last question.. Was it only MSI? I have no idea how MSI would cause this problem, but I wanted to ask for testing stuff (was gonna run a script that was just in an infinite wait, so I'll see if that causes this problem too).

Any more details would help. ;) (If it happened multiple times at a specific procedure/event/whatever, etc.)

It happened to me last night on all 3 instances of Smart + Simba I was running. I was using MSI, Ratinator, and my plank maker (Members+). All 3 crashed, and from what I gather, around the same time.

Was it within an hour, as Coh3n said? If so, it's definitely* a memory leak in Simba or SMART, and this started happening after the Simba update, not a SMART update, afaik, so I'll pretend I'm working on it by looking through the sawse but not really do anything because I don't know how to debug shit like that.

* I have no idea what the problem is.

From: i luffs yeww
Was it within an hour, as Coh3n said? If so, it's definitely* a memory leak in Simba or SMART, and this started happening after the Simba update, not a SMART update, afaik, so I'll pretend I'm working on it by looking through the sawse but not really do anything because I don't know how to debug shit like that.

* I have no idea what the problem is.

it was about an hour and a half into run time.

It just happened to me twice. The third try is still going (close to 4 hours now).

Huh. It may not be a memory leak actually.. If you've yet to restart, possibly something is just in an infinite loop.. Maybe an extension? Or a thread or something. I'll see if it happens to me.

From: i luffs yeww
Huh. It may not be a memory leak actually.. If you've yet to restart, possibly something is just in an infinite loop.. Maybe an extension? Or a thread or something. I'll see if it happens to me.

Yeah not sure. The only extensions I have enabled are MSI Player Remote (and it's been enabled since it was released, so I doubt that's the issue), DTM Editor, Explore Folders and Associate Files, all of which have been enabled just as long if not longer than the MSI remote.

Dgby has done updates to some stuff, explore folders is new, afaik (at least I haven't heard of it or seen it yet?). But if no new extensions could be the problem, it's either an infinite loop that's locking something up or.. I dunno. :x Getting Simba now to see if I can find anything.

From: i luffs yeww
Dgby has done updates to some stuff, explore folders is new, afaik (at least I haven't heard of it or seen it yet?). But if no new extensions could be the problem, it's either an infinite loop that's locking something up or.. I dunno. :x Getting Simba now to see if I can find anything.

Explore Folders

Had it ever since it was released. Thanks for checking it out by the way. :)

Ah. I remember that. It was never implemented into Simba by default, was it? :o

Anyway, I'm 99% sure it's not a memory leak, and so the only other thing is an infinite loop somewhere, I think. :x I'll just look at the changelog and hope for the best. :)

From: i luffs yeww
Ah. I remember that. It was never implemented into Simba by default, was it? :o

I don't think so, no.

Hm, just watched it completely crash. SMART and Simba both just suddenly closed. No error message, nothing. :unsure:

Been running 9 hours no crash.

0.95 gave me this problem though.

Would bot for 1 hour and it would be black screen. Never frozen just black screen.

0.96 fixed this problem for me.

From: Squancy
Been running 9 hours no crash.

0.95 gave me this problem though.

Would bot for 1 hour and it would be black screen. Never frozen just black screen.

0.96 fixed this problem for me.

Did you just install over top of 0.95 or did you uninstall 0.95, then install 0.96?

>_> Well huh. One thing I just noticed was..

"Do note that these is a API break in the Extensions; so Simba won't update itself for a week. It is highly recommended to reinstall Simba. Alternatively you can wait for the Simba auto update to kick in (a week from now); you'll also have to update your extensions manually after the update. See the news when you start Simba for more information on that. Sorry for that."

That could possibly somehow lead me to something or even contribute to the problem I guess.. I always hate when it works fine for some people and not for others. :(

There were so many updates I'm trying to figure out which could've affected this. I'm thinking it was either how the updater works now (not sure if it's different; haven't fully inspected), sockets (dunno why but I have an iffy feeling about them and have for awhile), or.. I have no idea. :p I hope everything was documented though, otherwise I will have problems finding it.

Wizzup? should be on soonish though so hopefully he'll figure it out. :p

EDIT:

>_> Now that I read what Squancy said, I have no idea where to look. I still feel like the infinite loop is a good option. Seems the sockets aren't causing the problem, and it shouldn't be an extension, either. I'm confus.

That is weird. I can't think of anything that could cause this right now. (I have to go soon)

If the issue is that bad, you could always go back to 0.94 for a short while. http://simba.villavu.com/bin/Release/

Also, this never happened with 0.95? Did you guys do a fresh install or ``install'' over the old Simba? (Perhaps it's some conflicting settings issue, but I'm completely guessing at the moment.)

Will have to look at the differences between the versions later. (Rather soon than later :) )

E: If it is an infinite loop and not a deadlock, then Simba/SMART should be using 100% CPU.

Been running a few different scripts haven't got any freezes in the past few hours (running all on diff vmachines)

I'm guessing it is just MSI

I uninstalled Simba, deleted C:\Simba, and installed 0.96 and still got this issue. Also note I had 0.94 previously installed, not Simba 0.95RC

Edit:

From: grats
Been running a few different scripts haven't got any freezes in the past few hours (running all on diff vmachines)

I'm guessing it is just MSI

No, it's not just MSI. It happened to two other scripts for me.

i've gotten that too. where my smart was black screen and the buttons down bottom were gone (disable smart, disable debug, disable graphics.)

I get this running the regular client, by the way.

… I do play legit, sometimes.

Now that I am not all sleepy, I may know that could possibly cause this. There were some changes in the plugin loader. They may have something to do with it. Especially if it only happens with SMART.

From: Nava2
I get this running the regular client, by the way.

… I do play legit, sometimes.

Interesting.

I just had this happen with both Simba's I was running last night. One after 4 hours, the other after 5. Although, it could have been something to do with it opening 100 recovery tabs. :(

From: Wizzup?
Now that I am not all sleepy, I may know that could possibly cause this. There were some changes in the plugin loader. They may have something to do with it. Especially if it only happens with SMART.

From: Nava2
I get this running the regular client, by the way.

… I do play legit, sometimes.

If N2 means without SMART, then does that change anything?

Its doubtful that its SMART related if it just came up. 6.6 has been out there for a while, and none of the script-callable routines can deadlock or otherwise hang since they are only able to be used from one thread anyway. Even if they did, it wouldn't cause the entire process to hang. If the GUI stops responding in both Java (i.e. SMART) and Pascal (i.e. Simba) then the MOST LIKELY CULPRIT is something that is causing the native event thread to hang (something related to forms), or running in the main Simba thread. (E: good luck finding it, too)

That's what I suspected as well, Ben. And since this has existed for at least two revisions, if not more, it should make it even more difficult to find. :/

May I suggest running Simba from the command line?

from cmd.exe:

Simba.exe > log.txt

Or:

Simba.exe 2>&1 > log.txt

Depending on how Windows works.

Then, if it crashes, look at log.txt (or paste it)
Might be helpful.

Also, does it also occur when not using any extensions?

From: Wizzup?
Also, does it also occur when not using any extensions?

If you're talking about just the updaters, then yes it happens if they're disabled.

I have associate, dtm_editor, msi_player_remote and explore_folders enabled.

From: Coh3n
If you're talking about just the updaters, then yes it happens if they're disabled.

I have associate, dtm_editor, msi_player_remote and explore_folders enabled.

I'm pretty sure he's talking about not using any extensions

How does this associate with SMART, Wizzup? I guess it's the loading / use of extensions that's interfering with plugins?

From: Wizzup?
May I suggest running Simba from the command line?

from cmd.exe:

Simba.exe > log.txt

Or:

Simba.exe 2>&1 > log.txt

Depending on how Windows works.

Then, if it crashes, look at log.txt (or paste it)
Might be helpful.

Also, does it also occur when not using any extensions?

I will run from the command prompt and disable all my extensions.

Also, today and yesterday I had SMART freeze, a black SMART screen, and 3 or 4 times, Simba/SMART just closed without error messages. I also got a couple access violations, but I'm not sure if that's related.

From: Wizzup?
May I suggest running Simba from the command line?

from cmd.exe:

Simba.exe > log.txt

Or:

Simba.exe 2>&1 > log.txt

Depending on how Windows works.

Then, if it crashes, look at log.txt (or paste it)
Might be helpful.

Also, does it also occur when not using any extensions?

I did what you posted (disabled all extensions, closed simba, cmd: cd C:\; cd C:\Simba; Simba.exa > log.txt) and I'll post what log.txt says later.

Thank you. That would be very helpful. I went over the difference between Simba 0.94 and Simba 0.96 with Raymond yesterday and we couldn't find something that could cause this. The issue may be that I compiled with a newer Lazarus, which could have had a bug / issue.

I guess I'll postpone the auto Simba update to 810 for a bit. ;)

From: Wizzup?
Thank you. That would be very helpful. I went over the difference between Simba 0.94 and Simba 0.96 with Raymond yesterday and we couldn't find something that could cause this. The issue may be that I compiled with a newer Lazarus, which could have had a bug / issue.

I guess I'll postpone the auto Simba update to 810 for a bit. ;)

If you think the compiler or newer libraries could be the problem, give one of my automatic builds a shot, since I haven't updated anything on there.

From: moparisthebest
If you think the compiler or newer libraries could be the problem, give one of my automatic builds a shot, since I haven't updated anything on there.

It could be a good idea to use Mopar's binary as well; just to see if a ``bad'' lazarus is indeed the issue. It's still weird though, since I just downloaded the nightly ``fixes'' branch, which should only be more stable. I suppose that's how Software Development goes… ;) Looking forward to those logs.

I'll also compile a Simba-0.94 and Simba-0.96 with the newest lazarus-fixes. I understand this is a broad range of Simba executables to test; but I'm really quite sure nothing in the Simba source could cause issues like this. At least, not when going from 0.94 to 0.96… :) I'll make a thread on it in a bit.

Okay well I ran 2 Simbas yesterday, and they both crashed. I forgot to disable all my extensions, but this is what came up in the command prompt. Both command windows were exactly the same. Hope it helps. :)

I see a very familiar error… Did you also save the text to a log file?

From: Wizzup?
I see a very familiar error… Did you also save the text to a log file?

Sorry no. I'll run it again later today probably, so I'll try to remember that and to disable all my extensions.

From: Coh3n
Sorry no. I'll run it again later today probably, so I'll try to remember that and to disable all my extensions.

Well, it was very useful. Note the "Failed to create new thread, code:8". Apparently Simba doesn't print the error now, and just stops right away. You can see it actually gracefully stops (going by the text anyway); since it does free smart. Did the Simba GUI disappear or freeze?

From: Wizzup?
Well, it was very useful. Note the "Failed to create new thread, code:8". Apparently Simba doesn't print the error now, and just stops right away. You can see it actually gracefully stops (going by the text anyway); since it does free smart. Did the Simba GUI disappear or freeze?

Yeah I know. I though "of course" when I saw the error. :p

The Simba GUI disappeared, as did SMART. I would think that's good, though. It closes properly rather than not responding.

This was still with the Simba binary from the installer (0.96) I suppose?

From: Wizzup?
This was still with the Simba binary from the installer (0.96) I suppose?

Yes.

http://msdn.microsoft.com/en-us/library/ms681382%28v=vs.85%29.aspx

Code 8 = Out of memory. So it could also be reflection/smart/dtms/bitmaps/ or something in Simba.

Looking forward to the other logs; by the way. Try to monitor your memory usage? :)

From: Wizzup?
http://msdn.microsoft.com/en-us/library/ms681382%28v=vs.85%29.aspx

Code 8 = Out of memory. So it could also be reflection/smart/dtms/bitmaps/ or something in Simba.

Looking forward to the other logs; by the way. Try to monitor your memory usage? :)

Will do.

Does MSI name it's DTMs and Bitmaps? If not then we definitely should name them…

From: Zyt3x
Does MSI name it's DTMs and Bitmaps? If not then we definitely should name them…

I didn't know you could until I saw Wizzup's tutorial. I think they should be named also.

As a point of reference, I have two nearly identical scripts, one color the other 99.9% color + 1 reflection procedure.

I can run 8 SMART instances with the pure color script for days on end with no errors. If I include reflection and use just GetItemsNear, TiletoMS and R_ChooseOption in an item picking function, I can still run 8 SMART instances, BUT the memory fills up after a few hours, and SMART instances randomly stop functioning and crash the script, one by one about 1-2 hours at a time.

And yes I set the GroundItemsArray := [] every time the function is called. So, there must be a memory leak somewhere in 1 of those 3 reflection functions, or something more global to do with including reflection at all.

In case you were wondering, the same thing happened when I disabled all the extensions.

Then the cause of the error is definitely in reflection..

From: tarajunky
As a point of reference, I have two nearly identical scripts, one color the other 99.9% color + 1 reflection procedure.

I can run 8 SMART instances with the pure color script for days on end with no errors. If I include reflection and use just GetItemsNear, TiletoMS and R_ChooseOption in an item picking function, I can still run 8 SMART instances, BUT the memory fills up after a few hours, and SMART instances randomly stop functioning and crash the script, one by one about 1-2 hours at a time.

And yes I set the GroundItemsArray := [] every time the function is called. So, there must be a memory leak somewhere in 1 of those 3 reflection functions, or something more global to do with including reflection at all.

Thank you!

I spent quite a few hours yesterday looking at the Simba changes… Really couldn't find anything. :)

Would this have anything to do with the SMART black screen problem? Lately I haven't even been able to run scripts without SMART going black after an hour or so. And I never minimize SMART.

From: Coh3n
Would this have anything to do with the SMART black screen problem? Lately I haven't even been able to run scripts without SMART going black after an hour or so. And I never minimize SMART.

I've been seeing a black screen happen + slight freezing a lot in ratinator recently, too.

and if you check stats you can see I've ran ratinator quite a bit

but so far… no problems at all with memory.

Smart have always been very laggy for me and it freezes when I mimize it a few times.
It does it even when I don't run any scripts.

Haven't been using smart much lately though…