C++ runtime error in v4.18... anybody else?
Hi folks,
I'm getting a lot of popups with "Microsoft Visual C++ Runtime Library - Assertion Failed!" erro messages when trying to apply scripts in version 4.18... I'd guess because of the change in js engine, but it could be something in my shambolic Windows setup I guess.
I'm just wondering if anyone else has encountered this:
https://drive.google.com/file/d/1Xai0xU1hwUAo8j8EY_gS7KM-vG5 J2OFe/view?usp=sharing
I thought I'd ask here before bothering Kim on support email, although he'll see it here of course.
EDIT: I just noticed that the consarned first line of the script was erroneous. Dag-nabbit. I'll recreate the script with correction and see what happens.
EDIT 2: Also incomplete "app.log(..." statements. I wouldn't expect any of this to throw a runtime library error, but what do I know...
EDIT 3: On further testing it *seems* to be the "app.log( " = " + )" statements that kill the program.
Best,
DF
I'm getting a lot of popups with "Microsoft Visual C++ Runtime Library - Assertion Failed!" erro messages when trying to apply scripts in version 4.18... I'd guess because of the change in js engine, but it could be something in my shambolic Windows setup I guess.
I'm just wondering if anyone else has encountered this:
https://drive.google.com/file/d/1Xai0xU1hwUAo8j8EY_gS7KM-vG5 J2OFe/view?usp=sharing
I thought I'd ask here before bothering Kim on support email, although he'll see it here of course.
EDIT: I just noticed that the consarned first line of the script was erroneous. Dag-nabbit. I'll recreate the script with correction and see what happens.
EDIT 2: Also incomplete "app.log(..." statements. I wouldn't expect any of this to throw a runtime library error, but what do I know...
EDIT 3: On further testing it *seems* to be the "app.log( " = " + )" statements that kill the program.
Best,
DF
Reply to #1:
Yes,
app.log( " = " + ); -- or similar -- causes the crash as you report.
But kudos to Aren for providing a somewhat useful message on the way down! So many programs don't.
Yes,
app.log( " = " + ); -- or similar -- causes the crash as you report.
But kudos to Aren for providing a somewhat useful message on the way down! So many programs don't.
Reply to #2:
Absolutely agree, Randy. Although most of the time with me it should just say
WARNING!
Loose NUT behind the keyboard!
:)
Absolutely agree, Randy. Although most of the time with me it should just say
WARNING!
Loose NUT behind the keyboard!
:)
Reply to #3:
Yes, I'm a frequent victim of PEBKAC errors and ID-10T crashes myself.
But to be fair, coding with Microsoft products is often worse than pulling teeth. ;)
Yes, I'm a frequent victim of PEBKAC errors and ID-10T crashes myself.
But to be fair, coding with Microsoft products is often worse than pulling teeth. ;)
Reply to #1:
It seems there is a problem with exception handling. I will release a fix within a day or two. Until then, don't write JS code with errors :-).
It seems there is a problem with exception handling. I will release a fix within a day or two. Until then, don't write JS code with errors :-).
Reply to #5:
HA!
HA!