Path: news.mathworks.com!not-for-mail
From: Brian Arnold <barnold@mathworks.com>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Matlab 7.4 OSX
Date: Fri, 18 May 2007 11:03:04 -0400
Organization: The MathWorks, Inc.
Lines: 72
Message-ID: <464DC028.3000301@mathworks.com>
References: <ef53b75.-1@webcrossing.raydaftYaTP> <ef53b75.0@webcrossing.raydaftYaTP>
NNTP-Posting-Host: arnoldb-mac1.dhcp.mathworks.com
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: fred.mathworks.com 1179500585 13340 144.212.108.69 (18 May 2007 15:03:05 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Fri, 18 May 2007 15:03:05 +0000 (UTC)
To: Roger Kylin <rkylin@segmail.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
In-Reply-To: <ef53b75.0@webcrossing.raydaftYaTP>
Xref: news.mathworks.com comp.soft-sys.matlab:409863



Hi,

Starting with R2007a, some products now require console access and do 
not require the JVM.   For example, Simulink now implements some 
non-X11-based windows.

You can work around this issue by using -nodisplay (or -nodisplay with 
-nojvm).  If you require graphics, you can save results to PDF or 
another format and view them in the Preview application.  If you really 
want to use an X11 display or forwarding, you can alternatively work 
around this issue by removing the console_owner check (which forces 
-nodisplay) from the $matlabroot/bin/matlab script, and using 
(undocumented) -noawt to significantly reduce the overhead of 
initializing the Java JVM.

The reason this new requirement is made at startup is because products 
which require console access also require a system call 
NSApplicationLoad on the main thread, which will initialize a CFRunLoop 
(the native Mac event loop), and run MATLAB on another thread. 
Previously, a CFRunLoop was only required for the Java JVM, but it is 
now required for products that don't use Java.  This all has to happen 
before MATLAB starts up.

This trend is expected to continue as we chip away at the X11/non-native 
aspects of MATLAB on Mac OS X, but at the same time we will still seek 
to find ways to continue to support the many non-console users, so 
continue to let us know how you are running MATLAB on the Mac.

We apologize for the difficulties this may have caused,

- Brian

Mac Developer
The MathWorks, Inc.


Roger Kylin wrote:
> ... I am seeing exactly the same problem... Matlab 7.4, OS 10.4.9,
> Powermac Quad 2.5 GHz. Works fine for Matlab 7.3.
> 
>  Timothy O'Keefe wrote:
>>
>> I am running OSX 10.4.9 on a PowerPC G5 (Dual 2.0 Ghz, 3.5GB RAM).
>> OpenSSH_4.2p1, OpenSSL 0.9.7l, XFree86 4.3.99.903(184).
>>
>> I upgraded from Matlab 2006b (7.3) to 2007a (7.4) and now I cannot
>> remotely invoke Matlab with disabled jvm.
>>
>> $ matlab -nojvm -nosplash
>>
>> Returns error:
>>
>> kCGErrorRangeCheck : Window Server communications from outside of
>> session allowed for root and console user only
>> INIT_Processeses(), could not establish the default connection to
>> the
>> WindowServer.Abort
>>
>> $ xeyes
>>
>> Shows up fine, and Matlab 7.3 works as well.
>>
>> Also, I don't know if this is a related issue in any way or a
>> separate issue altogether, but Matlab freezes periodically on Intel
>> Mac (iMac 2.0GHz Core Duo; 2 GB RAM). Both Matlab 7.3 and 7.4 are
>> being shared to machines via NFS.
>>
>> Again, this all used to work seamlessly with 2006b (and still
>> does).
>>
>> Thanks,
>> Tim O'Keefe