This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Choose Language Hide Translation Bar
TroyLarsen
TroyLarsen
Level I

Graph Builder Crashing as Variable Dragged Over

Feb 28, 2024 12:52 PM (313 views)

Hi,

I just installed a trial version of JMP 17. If I drag a variable to an axis in graph builder, I can see the chart update with the variable. As soon as I release "unclick" the variable, JMP crashes. 

 

I have used JMP 17 quite successfully in a past position.

 

I did uncheck the graphics acceleration as suggested in a related discussion.

 

I am using an Intel Iris Xe graphics card, but the driver version is newer than that suggested as a minimum in the bulletin. Computer is running Windows 10.

 

TroyLarsen_0-1709142701957.png

 

0 Kudos
2 REPLIES 2
GregF_JMP
Staff GregF_JMP
Staff

Re: Graph Builder Crashing as Variable Dragged Over

Feb 28, 2024 02:52 PM (303 views)  |  Posted in reply to message from TroyLarsen 02-28-2024

Hello Troy-
This is the user group discussion board, and perhaps someone may have some input- but please also take this up directly with JMP tech support by emailing support@jmp.com.

danschikore
Staff danschikore
Staff

Re: Graph Builder Crashing as Variable Dragged Over

Feb 28, 2024 04:49 PM (290 views)  |  Posted in reply to message from TroyLarsen 02-28-2024

After a crash occurs, on restart JMP may ask if you want to share the crash file with JMP.  If you do this, please include contact information and a brief description about what you were doing.  It may be helpful to know the analysis types of the columns you are using, which axis/role you are dropping into, other roles in use, etc.  The crash file will be sent to Tech Support and we can look it up to see if this has been investigated before, and hopefully fixed in a newer release.

0 Kudos