Raspberry Pi Forums

I've been happily exploring Mathematica on my Pi, but today came across an "INTERNAL SELF-TEST ERROR" crash which is reproducible every time I try it (on the same Pi).

Here is the synopsis of the message I sent to Wolfram Technical Support:

-- When exploring "PolyhedronData", I get the message immediately after typing the opening square bracket - independently of how long I delay that action ( so it's nor a time-dependent or system overload type of problem). --

I'm running Mathematica under the most recent version of Rasbian (via Noobs) on a Model B with 512 Mbytes of memory.

While waiting for Wolfram to respond, could a user or two try to replicate the error? Then I'd know if it is a true software bug, or just my RPi setup.

Thanks,
Alan.

Can you please post exactly what I can ctrl-v into mathematica to replicate your error?

Also, is this in Mathematica notebook, or does it happen in Wolfram command line also?

Thanks.

Yes, it is in Mathematica Notebook.

To try to replicate the problem, all you have to do is type "PolyhedronData [" .

The opening bracket should show the symptom.

Alan.

Okay, well I didn't get it throwing "PolyhedronData[" or ("PolyhedronData [") into a blank notebook, nor in the Wolfram command line.

Maybe it's your variables? Try playing around with ClearAll and trying it in a new notebook?
Maybe it's hardware? Is your RAM full? Do you have enough milliamps running to your Pi (1500)?

drxenocide wrote:Okay, well I didn't get it throwing "PolyhedronData[" or ("PolyhedronData [") into a blank notebook, nor in the Wolfram command line.

Maybe it's your variables? Try playing around with ClearAll and trying it in a new notebook?
Maybe it's hardware? Is your RAM full? Do you have enough milliamps running to your Pi (1500)?

Thanks for trying.

I have the same problem still on my brand-new Model B+ with a largely empty 8 Gb card and a stable 2000 mA power supply.
Curiously, more complex notebook entries work fine.

I'm awaiting a reply from Wolfram.

Alan.

Seems to be fixed in latest (July 2014) release.

Alan.