SRL Archive - Revisions / Releases

Tomorrow I'll put out a new Simba release + installer.

Interesting is that where won't yet be an actual Simba binary update (that would go with the auto updater anyway), but all the updates go right to the extensions. Unfortunately the script manager is not yet ready to be added to a new Simba, because it could otherwise update the extensions.

Extension fixes:

• Issues with srl.sex, reflection.sex, security.sex on Simba closing
• Crash in DTM editor when opened, closed and opened again. The fix will introduce a memory leak, but it is nothing serious and the real fix will have to wait until Nielsie comes back or someone feels like taking a crack at fixing it. It is much better than crashing anyway.
• DTM Output from DTM editor is now prettier. (Not just the raw DTM string)

I'll also provide a zip with the new extensions so you don't have to reinstall Simba just for the extensions. It is possible that the srl.sex and reflection.sex (and msi.sex?) will be bundled into one in this release, but I think that will have to wait until the next release.

Meanwhile, if the extension bugs really bother you, you can get them from the simba repos. http://git.villavu.com/?p=simba.git;a=summary (click on tree, then navigate to the extensions folder and redownload the extensions.)

If you know that it causes a memory leak, shouldn't it be rather simple to fix the memory leak..?

From: 3Garrett3
If you know that it causes a memory leak, shouldn't it be rather simple to fix the memory leak..?

Yeah removing the fix, means no memory leak; causes in crashes. DUH
He wouldn't posted it if it was that easy. cmon.
Wizzup how can we avoid the memory leak?

From: Hermen
Yeah removing the fix, means no memory leak; causes in crashes. DUH
He wouldn't posted it if it was that easy. cmon.
Wizzup how can we avoid the memory leak?

Suuucccckkk uuupppp

From: Griff721
Suuucccckkk uuupppp

In a way he is right. He obviously wouldn't post it if it wasn't a problem. And if it was easily solvable, it wouldn't be a problem.

@ *.sex -> sounds good.

~RM

From: 3Garrett3
If you know that it causes a memory leak, shouldn't it be rather simple to fix the memory leak..?

Crash is here:

procedure ResetBuffer;
begin
  if (bmpBuffer <> nil) then
    bmpBuffer.Free;

  bmpBuffer := bmp.Copy(0, 0, bmp.Width - 1, bmp.Height - 1);
  BufferChanged := False;
end;

First two lines. Or rather, it crashes in Free;
This can be cause by several things:

• We didn't export TMufasaBitmap properly. (I'm pretty sure we did export it correctly because .Free; works in other occasions)
• It indicates a deficiency in PascalScript. (Plausible)
• Somewhere in the code Nielsie frees bmpBuffer but doesn't set it to nil. (Or similar to this, code errors)

If it is the third option, then it may be not even introduce a memory bug, as the bitmap is already freed. If the code however somehow touches bmpbuffer and gives it a complete different value then calling .Free on it may fail. (It segfaults in pascalscript assembly, calling 'Free', which apparent is nil)

The memory leak isn't that bad either. It's not like it will add up 5 MB per minute. The only time it may leak (if at all) is when you open the DTM editor. (And possibly when selecting a new client image)

I didn't have much time to investigate yesterday. :)

do a grep on bmpBuffer, to check where it's been used ?

~RM