v3.14 Windows Map Part Image Crashing Bug

CheeToS2 · #1 02-06-2005, 05:12 AM

I've discovered a strange bug.
A certain image causes v3.14 windows to crash! I haven't verified it with the Mac and Linux clients.

WARNING TO OTHERS:
THESE STEPS WILL CAUSE YOUR CLIENT TO CRASH. FOLLOW THEM AT YOUR OWN RISK!
To recreate it:

1. Backup or delete the following file:
maps\parts\newmainmap\worlda-19.nw.png
(it is okay if you do not have it).

2. Put the following file in its place:

3. Run Graal v3.14 Windows

4. Log on to Graal2001 or Graal2001 Dev

5. (boom)

Renaming/deleting the file remedies the problem. Crashing does not occur on the latest v2 client.

Thanks to Tupper for verifying that it wasn't only me.

Ajira · #2 02-06-2005, 06:31 AM

Wow, this is in fact very weird. I'm not gonna try it just because it takes forever for Graal3 to close when it errors.

Benm00t · #3 02-06-2005, 03:59 PM

This might be because of the filename cache, which if you use (by default its set to on in the options), you will have to delete the FILENAMECACHE.txt which is located in the same folder as the client, every time you add/edit something yourself.

Ibonic · #4 02-06-2005, 04:40 PM

Quote:

Originally Posted by Benm00t

This might be because of the filename cache, which if you use (by default its set to on in the options), you will have to delete the FILENAMECACHE.txt which is located in the same folder as the client, every time you add/edit something yourself.

Only version 2 uses the filename cache as far as I know.

Quote:

A certain image causes v3.14 windows to crash

And the problem isn't limited to this specific image, but that's probably obvious.

Any image I replaced it with that had the same dimensions caused the client to crash, so maybe there just isn't enough error checking done - e.g. the client (maybe even through script) could be expecting something to be a certain way, and pukes if it's not. But I don't know, it's silly for me to assume what's happening without seeing the code; Stefan will have to look into it

Benm00t · #5 02-06-2005, 04:50 PM

Quote:

Originally Posted by Ibonic

Only version 2 uses the filename cache as far as I know.

err... yes you're right... all these versions that are out now confused me. Sorry :-P

CheeToS2 · #6 02-06-2005, 07:08 PM

Hmm, I decided to do some more research into it:
1) It seems that ANY file named worlda-19.nw.png will cause it to crash. To test this, I grabbed one of the map part images that didn't make it crash and renamed it to worlda-19.nw.png. (Oops, sorry Ibonic, this is what you did; I misread your post).

2) Entering worlda-19.nw causes the client to crash.

3) Copying worlda-19.nw and renaming it (to testworld.nw), and entering the copied level does not cause the client to crash.

4) I thought that it might have something to do with newmainmap.txt, but it looks fine to me.

Is worlda-19 a symbol of the devil?

Admins · #7 02-07-2005, 04:47 AM

Works with other map parts >=19 too, it's bugging both v2.3 and v3.1, but v2.3 is most of the time not crashing, while v3.1 is most of the time crashing. It's fixed in v3.15, will upload that soon.

CheeToS2 · #8 02-07-2005, 05:08 AM

Quote:

Originally Posted by Stefan

Works with other map parts >=19 too, it's bugging both v2.3 and v3.1, but v2.3 is most of the time not crashing, while v3.1 is most of the time crashing. It's fixed in v3.15, will upload that soon.

Ok, thank you

Alexander · #9 02-09-2005, 06:36 AM

Does mng files cause you to crash at all?

Admins · #10 02-09-2005, 01:45 PM

Quote:

Originally Posted by Alexander

Does mng files cause you to crash at all?

They don't crash the client, but you can have an endless animation without delays between the frames, which then cause the mng reader to freeze. I have fixed that though.