I’m wondering maybe, if an SE working on a Mac – sent in this Crash file late yesterday, 9/30 about 5:25?
It appears they were using JMP 15EA8 – anything else you can share would be great – is this repeatable?
Thanks,
Mandy
Mandy Chambers
Principal Test Engineer ▪ JMP Testing ▪ JMP R&D
Tel: + 1 919 531 7562 ▪ Mandy.Chambers@jmp.com
www.sas.com
SAS® … THE POWER TO KNOW®
From: Mandy Chambers <Mandy.Chambers@jmp.com>
Date: Tuesday, October 1, 2019 at 9:33 AM
To: Shannon Conners <Shannon.Conners@jmp.com>
Subject: FW: [SAS 7612902552] Update
Any idea who sent this in?? it seems like it is in house. It is a Mac Crash..
Process: JMP [68401]
Path: /Applications/JMP Pro 15.app/Contents/MacOS/JMP
Identifier: com.sas.jmp
Version: 15.0b8 (361858)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: JMP [68401]
User ID: 501
Date/Time: 2019-09-30 14:04:49.470 -0700
OS Version: Mac OS X 10.14.6 (18G95)
Report Version: 12
Bridge OS Version: 3.6 (16P6571)
Anonymous UUID: 4BB1594F-56B5-80EF-9455-D26D1FE54686
Time Awake Since Boot: 450000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_ARITHMETIC (SIGFPE)
Exception Codes: EXC_I386_DIV (divide by zero)
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Floating point exception: 8
Termination Reason: Namespace SIGNAL, Code 0x8
Terminating Process: exc handler [68401]
Application Specific Information:
Performing @selector(buttonAction
from sender JMPButton 0x6000038eac40
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.sas.jmp 0x000000010044aa11 0x1001d2000 + 2591249
1 com.sas.jmp 0x0000000100900289 WAxis::niceDateScale(NumDataFormat const&, double, double, double, double, double, double) + 1985
2 com.sas.jmp 0x0000000100340f16 Term::doScale(double, double, bool, long) + 854
3 com.sas.jmp 0x00000001013d32d0 0x1001d2000 + 18879184
4 com.sas.jmp 0x00000001013547f0 0x1001d2000 + 18360304
5 com.sas.jmp 0x0000000101352c65 0x1001d2000 + 18353253
6 com.sas.jmp 0x0000000101351d53 0x1001d2000 + 18349395
7 com.sas.jmp 0x000000010230b817 launchPlatform(EPlatform, JString const&, DataTable*, PlatformParms*, DisplayBox*, Top*, EvalContext*, Scriptable**, PlatformLaunchInfo*, bool, LaunchHelper const*, std::__1::shared_ptr) + 12078
8 com.sas.jmp 0x00000001020c5ec2 PlatformDlg::actionGo(PlatformLaunchInfo*) + 1346
9 com.sas.jmp 0x00000001020c5607 PlatformDlg::actionButton(int) + 51
10 com.sas.jmp 0x00000001020d6693 0x1001d2000 + 32523923
11 com.sas.jmp 0x0000000100ac8e5b ButtonDisplay::clickAction(GCanvas&, generic_point const&, int) + 517
12 com.sas.jmp 0x0000000100ac6e16 ButtonDisplay::buttonClickAction() + 642
13 com.sas.jmp 0x0000000102ef9288 0x1001d2000 + 47346312
14 com.sas.jmp 0x0000000102ef91f7 0x1001d2000 + 47346167
15 com.apple.AppKit 0x00007fff40465644 -[NSApplication(NSResponder) sendAction:to:from:] + 312
16 com.apple.AppKit 0x00007fff404cf992 -[NSControl sendAction:to:] + 86
17 com.apple.AppKit 0x00007fff404cf8c4 __26-[NSCell _sendActionFrom:]_block_invoke + 136
18 com.apple.AppKit 0x00007fff404cf7c6 -[NSCell _sendActionFrom:] + 178
19 com.apple.AppKit 0x00007fff404fc54b -[NSButtonCell _sendActionFrom:] + 96
20 com.apple.AppKit 0x00007fff404ce0e1 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 2375
21 com.apple.AppKit 0x00007fff404fc29c -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 698
22 com.apple.AppKit 0x00007fff404ccb1e -[NSControl mouseDown:] + 791
23 com.apple.AppKit 0x00007fff403a8937 -[NSWindow(NSEventRouting) _handleMouseDownEvent:isDelayedEvent:] + 5724
24 com.apple.AppKit 0x00007fff402df1a6 -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 2295
25 com.apple.AppKit 0x00007fff402de667 -[NSWindow(NSEventRouting) sendEvent:] + 478
26 com.apple.AppKit 0x00007fff4017de6b -[NSApplication(NSEvent) sendEvent:] + 331
27 com.apple.AppKit 0x00007fff4016c5e0 -[NSApplication run] + 755
28 com.apple.AppKit 0x00007fff4015bae8 NSApplicationMain + 777
29 com.sas.jmp 0x00000001038a6a9d 0x1001d2000 + 57494173
30 libdyld.dylib 0x00007fff6ef753d5 start + 1
This crash report is from the JMP download server. Please see the attached file(s) for detailed information.
------------------ User-provided information is below -------------------
I opened JMP 15, ran a simple Compile CSV Add-In (that concatenates sevreral CSV files with the same columns / headers into 1x JMP table). Once the file was fully concatenated (from 5x individual files), I scanned what appeared to be an appended column, and found data that belonged to an earlier column -- I then selected those cells and performed a CTRL-X, click destination cells (a couple columns to the left, but only the first cell), and CTRL-V to paste in the block of cells. JMP crashed.
Mandy Chambers
Principal Test Engineer ▪ JMP Testing ▪ JMP R&D
Tel: + 1 919 531 7562 ▪ Mandy.Chambers@jmp.com
www.sas.com
SAS® … THE POWER TO KNOW®
From: "cloudproxy._JMP__JMP_BETA" <jmpbeta@jmp.com>
Date: Tuesday, October 1, 2019 at 7:25 AM
To: Mandy Chambers <Mandy.Chambers@jmp.com>
Subject: [SAS 7612902552] Update
|
Mandy,
Please investigate the following beta report. If you enter anything in defects, use the keyword JMP15EA8 (if the report is from an internal employee, use your judgment as to whether the keyword is appropriate or not).
If I have sent this to the incorrect tester, please forward to the appropriate tester and cc me.
If you need more information and the customer is an internal person (jmp or sas email address), please contact the employee directly and cc me so that I know the issue is being taken care of.
If the track/email is from JMP Tool, it means the track was submitted anonymously and we have no way of contacting the customer. Do the best you can with these tracks and let me know the outcome.
Thanks,
Tonya Mauldin
JMP Testing
http://sirius.na.sas.com/Sirius/ShowTrack.aspx?trknum=7612902552
|
|
|
|
|
