When used into max world, exceptions and exit statements like 

System.exit(1) lead to a major windows crash (i mean over 100% for 

20min, no way to get the task manager up, dirty reboot). Is it just me 

or do we have to define another way to terminate the process when we got 

an execption ? What if we just keep, for example, the 

e.printStackTrace();, but erase the System.exit(1); ??

f.e chanfrault | aka | personal computer music

> >>>>>> objects for max/msp | C, java & python

When used into max world, exceptions and exit statements like 
System.exit(1) lead to a major windows crash (i mean over 100% for 
20min, no way to get the task manager up, dirty reboot). Is it just me 
or do we have to define another way to terminate the process when we got 
an execption ? What if we just keep, for example, the 
e.printStackTrace();, but erase the System.exit(1); ??

-- 
f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> objects for max/msp | C, java & python


system-exit1-troubles

I don't think the jvm can quit max this way (ben or topher, correct me 

I found a workaround by sending a bang in a

If your error appears at object instantiation, use the bail() method 

Exceptions should be caught and they should terminate the process only 

In my opinion, you should output major errors to max window or to a log 

I don't think the jvm can quit max this way (ben or topher, correct me 
if i'm wrong).
I found a workaround by sending a bang in a
[; max quit] messagebox.

If your error appears at object instantiation, use the bail() method 
(like bogus).

Exceptions should be caught and they should terminate the process only 
when major errors appears.
In my opinion, you should output major errors to max window or to a log 
file.

Thanks again, Leopold. I forgot about bail()...

f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> objects for max/msp | C, java & python

System.exit(1) troubles