Re: [Fwd: Re: usage of inline and fminbnd] error: memory exhausted -- trying to return to prompt

[David Bateman]

shoker_17 wrote:
> Each image is of size 158x103 pixels. What i was doing was to extract the
> features of the images and save them in high dimensional space for
> classification. I guess ur explanation could be one of the possible reasons.
>
> Shoker
>
>
> Michael Grossbach wrote:
>   
>> shoker_17 wrote:
>>     
>>> May I know if anyone knows the root of the cause?
>>>       
>> Maybe memory exhaustion? ;)
>> Have you done a rough estimation of how big your images are and if that 
>> amount of information is possibly bigger than your physical memory?
>> What do you mean by saving it as a text file? Convert the binary data 
>> into ASCII? ASCII takes a lot more space compared to binary data, maybe 
>> that's the point where should start looking.
>>
>> HTH, Michael
>> _______________________________________________
>> Help-octave mailing list
>> address@hidden
>> https://www.cae.wisc.edu/mailman/listinfo/help-octave
>>
>>
>>     
>
>   
What version of octave? What is an example of the code that tickles the
problem.. I can think of a couple of things to do with mex and function
handles that were fixed between 2.9.9 and the current CVS that might be
related to this, but with no code or information of what version of
octave you are using then I can't help..

D.


-- 
David Bateman                                address@hidden
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary