[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #35546] imresize produces memory exhausted err
From: |
Ian Journeaux |
Subject: |
[Octave-bug-tracker] [bug #35546] imresize produces memory exhausted error |
Date: |
Thu, 16 Feb 2012 14:16:44 +0000 |
User-agent: |
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; SU 3.95; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; AskTbARS/5.11.1.15497) |
URL:
<http://savannah.gnu.org/bugs/?35546>
Summary: imresize produces memory exhausted error
Project: GNU Octave
Submitted by: ijourneaux
Submitted on: Thu 16 Feb 2012 02:16:42 PM GMT
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Assigned to: None
Originator Name: Ian Journeaux
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 3.6.0
Operating System: Microsoft Windows
_______________________________________________________
Details:
This may not be a bug and could be a result of a change in the memory
footprint of Octave 3.6.0 compared to 3.2.4.
I am trying to convert code that I have working with 3.2.4 over to octave
3.6.0 (Windows Mingw version).
In my code, I load an large image with imread and then try to resize the image
using
AA=imread(T1);
aa1=imresize(AA,0.1);
Under 3.6.0 this produces the following error
error: memory exhausted or requested size too large for range of Octave's
index type -- trying to return to prompt.
Were there cahnges to the underlying routines used by imresize that would ahev
affected the efficiency of memory use?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?35546>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #35546] imresize produces memory exhausted error,
Ian Journeaux <=