octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #59242] ind2rgb/ind2gray errors with uint inpu


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #59242] ind2rgb/ind2gray errors with uint input containing the maximum integer value outside of colormap range
Date: Fri, 9 Oct 2020 12:01:20 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36 Edg/85.0.564.70

Follow-up Comment #5, bug #59242 (project octave):

@gyom: That sounds reasonable to me. But like Niklas pointed out, `x` could be
very large. Changing one single value in `x` could lead to twice the memory
being required.
Preparing for both cases (large maps or large images) is probably the best way
forward.
We can think about the case where both the map and the image are large when
this is a problem for someone...

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59242>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]