11
$\begingroup$

Bug introduced in 10.0 and persisting through 11.0.1
InfiniteLine is new in 10.0.

[CASE:3840702] From your description, I gather you are noticing an unexpected crash while trying to evaluate Graphics@InfiniteLine@{{0,0},x} .

I tested and confirmed your issue and have passed it along to our developers for further diagnosis. -- WRI


I reported this to WRI:

This works fine:

Graphics@InfiniteLine@{{0, 0}, {1, 1}}

This crashes the Front End.
WARNING: A Front End crash results in losing all unsaved work!

Graphics@InfiniteLine@{{0, 0}, x}

Does this happen on everyone's system or is it specific to mine?

$\endgroup$
  • $\begingroup$ Confirmed on Win10 V11.0.1 $\endgroup$ – Kuba Feb 15 '17 at 15:53
  • $\begingroup$ Crashes all (FE+Kernel) on OSX 10.11 and MMA v 11.0.1. Actually it crashes whatever x is (integer, real, ...). $\endgroup$ – SquareOne Feb 15 '17 at 16:07
  • $\begingroup$ @SquareOne Really? It does not crash on my system if x is defined to say (1,1). It only crashes when it is undefined, ie. symbolic I thought. $\endgroup$ – masterxilo Feb 16 '17 at 12:14
  • 1
    $\begingroup$ @masterxilo If you replace x with something which is NOT at least a pair of two parameters {_,_}, yes it crashes it all for me. For example replace x with 1 or 16.2 or {12} or any string like : Graphics@InfiniteLine@{{0, 0}, "hello"}, ... $\endgroup$ – SquareOne Feb 16 '17 at 17:50
3
$\begingroup$

Fixed in 11.1 (windows). No crash. Just an error message

$Version

11.1.0 for Microsoft Windows (64-bit) (March 13, 2017)

Graphics@InfiniteLine@{{0, 0}, x}

Mathematica graphics

$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.