 |
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
 Posted: Thu Jul 29, 2010 2:37 am
Unknown Problem (Fatal Trigger Error)
|
Well I have no idea what is happening. However, I made some adjustments to a package, nothing of which would have caused this error that I can see and suddenly I can no longer use the package at all. Every time I open it Cmud starts firing all the triggers. It's just crazy. It keeps saying indefinite loop in all my triggers and everywhere. I'm just sitting there clicking disable trigger on the Fatal Trigger Error popups and then it just pegs my CPU and completely Locks up. I can also see stuff printing to screen where triggers are firing. I can't figure out at the moment how to somehow disable the damn thing to get in there to see what is happening because it happens as soon as I open Cmud and the package. Any ideas? I'm at a loss as to what happened. I've not had any problems really lately and BOOM it just goes haywire!
|
|
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Thu Jul 29, 2010 2:53 am
|
Additionally the stuff printing to the screen from random triggers firing for no reason is from the #PRINT command so they shouldn't be firing triggers either since #print bypasses triggers. Either way, this is some fatal error with Cmud perhaps because even the alarm triggers are firing and saying they have indefinite loops. How exactly can Alarm triggers be firing in indefinate loops?
|
|
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Thu Jul 29, 2010 3:16 am
|
Okay I was able to turn off all triggers and narrow this down. It seems when I tried to delete a row from a variable stringlist it deleted the entire variable somehow. The trigger pattern which used the variable stringlist like \b(?:@varList)\b was firing everything in the package somehow because varList did not exist. I created a new varList and added values and now it works. It also says indefinite loop with a fatal trigger error if varList is there but is empty.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Jul 29, 2010 5:02 pm
|
The error about the trigger is correct for when the varList is empty. The actual bug seems to be whatever caused your variable to get deleted, so if you can reproduce a way to cause the variable to be deleted by just deleting a row, please post a procedure for that. I just played with it here and wasn't able to delete the entire variable by deleting a row in a string list, so the exact steps of the procedure matter.
|
|
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Thu Jul 29, 2010 7:52 pm
|
Well I don't remember deleting it but maybe I did. I kept clicking to disable the trigger on the Fatal Trigger Error popup and it would just lock up Cmud. To be honest ever since JSON was implemented I have had nothing but problems with stringlists.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Fri Jul 30, 2010 4:25 pm
|
| Quote: |
| To be honest ever since JSON was implemented I have had nothing but problems with stringlists. |
Well, that's because the underlying low-level code was completely rewritten from scratch. This wasn't done just to use JSON, it was done to properly support nested string lists and database variables, which was a very common support request.
Obviously rewriting the low-level string list data routines is going to introduce a lot of problems. That's exactly why this is still a Beta release. That's why I've done over a dozen version releases in the past couple of months. If you are still having troubles with 3.22, then you need to post good bug reports showing how to reproduce the problems just like with any other bugs. |
|
|
|
|
|
|
|
