4D v2004 crashing problem
Norman Kinsey (7/22/08 4:59PM)
Matthias Schmidt (7/23/08 9:21AM)
Norman Kinsey (7/22/08 4:59 PM)
We have just upgraded to Leopard (10.5.4) and 4D v2004.7 (most recent
download from 4D). The new Mac is a MacPro Dual 3.2Ghz x 4 Core Intel
Xeon
with 4GB RAM/ Apple RAID with 256MB Write Cache with 2x15K SAS drives
The computer runs VERY fast and handles thousands of TCP/IP
transactions
(using ITK) for 1-2 hours then crashes. The system log is below:.
Does anyone have any ideas or suggestions to keep 4D from crashing?
Are there any issues with 4D v2004.7 / Leopard / Intel Macs?
Jul 22 13:10:37 greaves-travel sshd[133]: USER_PROCESS: 133 ttys000
Jul 22 13:10:37 greaves-travel com.apple.launchd[1]
(0x10af90.sshd[133]):
Could not setup Mach task special port 9: (os/kern) no access
Jul 22 13:10:39 greaves-travel kextd[10]: writing kernel link data to
/var/run/mach.sym
Jul 22 13:30:26 greaves-travel com.apple.launchd[1]
(0x113600.Locum[200]):
Exited: Terminated
Jul 22 14:05:17 greaves-travel ReportCrash[266]: Formulating crash
report
for process 4th Dimension[201]
Jul 22 14:05:17 greaves-travel ReportCrash[266]: Saved crashreport to
/Library/Logs/CrashReporter/4th
Dimension_2008-07-22-140517_TABS-US-Live.crash using uid: 0 gid: 0,
euid: 0
egid: 0
Jul 22 14:05:17 greaves-travel
com.apple.launchd[1]([0x0-0x1b01b].com.4D.4D[201]): Exited abnormally:
Bus
error
Jul 22 14:17:48 greaves-travel sshd[123]: DEAD_PROCESS: 133 ttys000
Jul 22 14:17:54 greaves-travel sshd[302]: USER_PROCESS: 302 ttys000
Jul 22 14:17:54 greaves-travel com.apple.launchd[1]
(0x113e10.sshd[302]):
Could not setup Mach task special port 9: (os/kern) no access
Jul 22 15:08:16 greaves-travel ReportCrash[412]: Formulating crash
report
for process 4th Dimension[276]
Jul 22 15:08:16 greaves-travel ReportCrash[412]: Saved crashreport to
/Library/Logs/CrashReporter/4th
Dimension_2008-07-22-150816_TABS-US-Live.crash using uid: 0 gid: 0,
euid: 0
egid: 0
Jul 22 15:08:16 greaves-travel com.apple.launchd[1]
([0x0-0x1f01f].com.4D.4D[276]): Exited abnormally: Bus error
Matthias Schmidt (7/23/08 9:21 AM)
Am/On Tue, 22 Jul 2008 16:59:20 -0500 schrieb/wrote Norman Kinsey:
We have just upgraded to Leopard (10.5.4) and 4D v2004.7 (most recent
download from 4D). The new Mac is a MacPro Dual 3.2Ghz x 4 Core Intel
Xeon
with 4GB RAM/ Apple RAID with 256MB Write Cache with 2x15K SAS drives
The computer runs VERY fast and handles thousands of TCP/IP
transactions
(using ITK) for 1-2 hours then crashes. The system log is below:.
Does anyone have any ideas or suggestions to keep 4D from crashing?
Are there any issues with 4D v2004.7 / Leopard / Intel Macs?
Jul 22 13:10:37 greaves-travel sshd[133]: USER_PROCESS: 133 ttys000
Jul 22 13:10:37 greaves-travel com.apple.launchd[1]
(0x10af90.sshd[133]):
Could not setup Mach task special port 9: (os/kern) no access
Jul 22 13:10:39 greaves-travel kextd[10]: writing kernel link data to
/var/run/mach.sym
Jul 22 14:05:17 greaves-travel
com.apple.launchd[1]([0x0-0x1b01b].com.4D.4D[201]): Exited abnormally:
Bus
error
Jul 22 14:17:48 greaves-travel sshd[123]: DEAD_PROCESS: 133 ttys000
Jul 22 14:17:54 greaves-travel sshd[302]: USER_PROCESS: 302 ttys000
Jul 22 14:17:54 greaves-travel com.apple.launchd[1]
(0x113e10.sshd[302]):
Could not setup Mach task special port 9: (os/kern) no access
([0x0-0x1f01f].com.4D.4D[276]): Exited abnormally: Bus error
what does the crash report say?
What was USER_PROCESS: 133? Is it connected to ITK?
I'd assume, you will need to rewrite the ITK code to NTK and for best
performance upgrade the app to v11.
ITK (as well as 4D 2004) is running through rosetta and as far as I got
it from the recent discussions on the list ITK is a dead product.
cheers,
Matthias
------------------------------------------------------------------------
Admilon Consulting GmbH
Am Wiesengrund 9a, 90584 Allersberg, Germany
Geschäftsführer: Peter Frank, Matthias Schmidt
Amtsgericht Nürnberg: HRB 21750
Tel.: +49-9174 - 6646 Fax: +49-9174 - 6647
<http://www.admilon-consulting.de>
Reply to this message
Summary created 7/23/08 at 2:07AM by Intellex Corporation
Comments welcome at: feedback@intellexcorp.com