nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unstable script

David_Burnham

I have a script that isn't doing what I want it to do. so I add a trivial diagnostic to help trace what is going on:

show("here");

But when I do this it causes JMP to crash.

I just wonder if anyone else has come across this type of problem.

I know it's not much to go on!

Accepted answers

Craige_Hales

If it crashed, it is a bug in JMP. If you get some sort of crash file, that might help us figure it out.

Just guessing, I imagine there are display boxes and closed reports involved, and somehow there is a JSL variable that is pointing to a display box that is deleted. Depending what has happened to that memory since it was deleted, bad things may happen. Or maybe nothing. Writing to the log, with show or print, is likely to trigger some display box clean up, and possibly the crash.

We put a lot of work into JMP 15 to handle display boxes in a more state-of-the-art way; you might get a better diagnostic out of an early adopter JMP 15.

All comments

vince_faller

Nope. Just ran it alone and it doesn't happen to me. In regular code, I don't often show() for non-variables, I usually print().

Mark_Bailey

Is this behavior reproducible? What happens after JMP crashes and you re-start it?

txnelson

Dave,
I am not having any issue with this, running under Windows 10, with JMP Pro 14.3

David_Burnham

Some updates:

This problem is occurring on MacOS. It works fine on Windows. I was running 14.2 and have upgraded to 14.3 and the problem still occurs.
The problem is repeatable, although I think I would struggle to create a simple sample script that exhibits the same behaviour.
The only reason I have a "show" is because the real code was causing a crash and I using show statements to trace execution. But even with the most trivial code I could think of - just the "show" - the problem still occurred. BUT - if I replace "show" with "print" then the crash doesn't occur! So that is progress!

David_Burnham

As I said, "print" is working, but it was really just a place holder for some other code that was causing a crash.

I've done some more testing. This is starting to feel like Schrodingers cat.

I have restored the original code.

If I restart JMP and run the script it fails. If I restart JMP and open the script - look at it, to remind myself what it looks like - then close the script and run it, it works.

Craige_Hales

If it crashed, it is a bug in JMP. If you get some sort of crash file, that might help us figure it out.

We put a lot of work into JMP 15 to handle display boxes in a more state-of-the-art way; you might get a better diagnostic out of an early adopter JMP 15.