Xindaris
Level: Smitemaster

Rank Points: 1609
Registered: 06-13-2015
IP: Logged

File: Error.hold (78.5 KB)
Downloaded 44 times.
License: Public Domain

(Encountered on version 5.1.0.6512)

I don't really even comprehend what I'm encountering here, so I'll just describe what I've discovered:

-Attached is a hold containing a copy of a particular room from a hold I'm working on, with some fairly extensive custom element coding and a time token. The relevant room is 1E in this hold.
-Attached to my next post in this thread will be a demo for said room.

-Playing the demo at "normal speed" (by just choosing to watch it), playing the room, and advancing the demo slowly, all don't seem to break anything.
-Playing the demo quickly by holding down the "east" key seems to crash DROD...sometimes? It seems like doing this multiple times in the same DROD session makes it more likely to crash. Also, watching other demos for a bit and then doing this seems more likely to make it crash than watching it the first time.
-My computer also plays a "bling" sound like it does when too many keys are being pressed at once when the crash occurs, even though I'm still only pressing one key at the time (the "east" key).
-DROD.err is blank after this particular crash.
-My attempts to isolate the specific cause of this crash have been in vain.

____________________________
109th Skywatcher

Here are some links to Things!

---

[Last edited by Xindaris at 08-15-2016 08:24 PM]

Xindaris
Level: Smitemaster

Rank Points: 1609
Registered: 06-13-2015
IP: Logged

File: Error Crash 1E Victory.demo (979 bytes)
Downloaded 45 times.
License: Public Domain

Attached to this post is the violating demo.

I originally discovered the issue with the room in its original setting, with someone else's demo, and the specific sequence of moves doesn't seem to be the problem, but it seems like the fact that this solution involves "blocking" the timeclone with Beethro's body at several points is important to the crash because a different demo with a solution not involving "blocking" the timeclone at all does not cause a crash.

____________________________
109th Skywatcher

Here are some links to Things!

disoriented
Level: Smitemaster

Rank Points: 2424
Registered: 08-07-2007
IP: Logged

I think I also encountered this crash. Reported it here (I was running the Mac version):

http://forum.caravelgames.com/viewtopic.php?TopicID=41353

____________________________
34th Skywatcher

Best to PM me, since I might miss your message on CaravelNet chat.

mrimer
Level: Legendary Smitemaster

Rank Points: 5199
Registered: 02-04-2003
IP: Logged

skell, is this the same issue as you just fixed?

____________________________
Gandalf? Yes... That's what they used to call me.
Gandalf the Grey. That was my name.
I am Gandalf the White.
And I come back to you now at the turn of the tide.

skell
Level: Legendary Smitemaster

Rank Points: 3776
Registered: 12-28-2004
IP: Logged

I've replayed the demo in the hold 5 times on max speed (by holding right arrow key) in the latest build and did not get a crash. The description sounds like it was the same problem.

I'll mark it as fixed.

____________________________
My website

---

[Last edited by skell at 10-03-2020 07:22 PM]

Xindaris
Level: Smitemaster

Rank Points: 1609
Registered: 06-13-2015
IP: Logged

Yes, there was speech in the relevant room here too, so I think it's likely the same bug. I just made an assumption that it had to do with the custom element when I first wrote the top post.

____________________________
109th Skywatcher

Here are some links to Things!

kieranmillar
Level: Smitemaster
Rank Points: 3145
Registered: 07-11-2014
IP: Logged

Can confirm I also cannot replicate the crash in 5.1.1.alpha.2020-10-16. I note that in the demo there is a character with a speech file where the timing just so happens to stop talking right around the time the timeclone reset happens if you run the demo at full speed, so I can see why faster computers might get there just in time to cause a crash. That would make it the same issue as the other thread, so I believe this has been fixed.