Glad to see somebody on Windows got the same "kernel exited" problem. I changed from Windows to Mac almost at the same time as I upgraded to Mathematica version 10. I use a lot of ParametricPlot3D and never got a problem in versions prior to 10. With 10.01 nd 10.02 I started getting this problem very often. It got much better in 10.2 and I even informed Tech Support the problem was probably solved. But it happens still albeit less frequently and the kernel exits and I get:"The kernel Local has quit (exited) during the course of an evaluation" during Manipulates with ParametricPlot3D It has in my experience to do with graphics and with continuous updating of plots or manipulate. I leaned to live with it but it has something to do with version 10. Maybe Wolfram solves this in next version? Or informs us of some setting that can avoid, circumvent or eliminate this?

Hello David,

thank you very much for your good news. You could run up to a larger t by increasing the quantity tfr ( = time final relative) by shifting the corresponding slider to the right. Since the failures observed on my system seemed to occur at random, running longer gives failure a greater chance. Changing n (e.g. from 64 to 200, need not be a power of 2) increases the workload and memory consumption considerably and - unfortunately - takes more from your time. Perhaps such increased workload is a problem even for your strong system.

Would be great hearing more of your experiences.

Regards Ulrich

Actually it turned out that the run went with tfr =5 and n=64. The calculation stopped at t=10.6719s. Are the .pdf files of any interest to you?

On my system what happens is not spectacular but also not nothing. The activity of a cell which is normally indicated by a yellow vertical bar stops and the check mark of the make box disappears. If this has happened you should invoke the 'run'-box and then the kernel may exit spontaneously after a while or the program will end regularly (again the yellow cell bar vanishes, the run-checkmark disappears. A new sequence 'change sliders', 'make', 'run' may be started. Good luck!

Regards Ulrich

Extremely sorry Hans,

my intention was to refer to the checkboxes in the user interface of my Manipulate. There are boxes such as 'run', 'reset', 'make', 'take' above the area where the many sliders are placed. Invoking the check boxes means clicking on them. Sorry for having used slang instead of clear language. Hope this helps. Of course, you are well-come to ask whatever comes up.

Regards Ulrich

Sorry Hans, I should have told you.

The job 'runs' which in this case means only that it waits until 'make' is invoked. (Before you invoke 'make' you could play arround with the sliders to set the inititial state of the system. Ignore this option at first.) When 'make' came to an end , which is after less than a minute for the preset values (n is the most influential quantity), you invoke 'run' and sometimes the run comes to its regular preset end and sometimes it ends with a beep and an inactive local kernel. In running, five pdf-files will be written to a place which depends on the systems (sorry for the inconvenience).

I look forward to your experiences! Regards Ulrich

Now my system doesn't crash, and the job runs, but does nothing. I should invoke "make", which means what...?

That sounds good. But in addition think about the amount of memory the manipulate-object may need. I noticed that you arranged for the change of quite a lot of parameters.