Re: si runs out of contiguous memory

2016-02-22 Thread Luc-Eric Rousseau
It's possible the message is coming up with other types memory
allocations as well, for example a big weight maps or other big
arrays.
Check if it's a a really big number. It's in bytes, I think, so you
would device by 1024*1024 to get a number in megs.
if the original number is greater than 2 bilions bytes, it would
likely be a bug somewhere.

On 22 February 2016 at 10:37, Matt Morris  wrote:
> That's exactly the error message I'm getting, though I don't think I have
> any images loaded - all my viewports are wireframe or shaded, and the
> textures that are linked on the character are not linked up (remote job,
> only have the model).
>
>
> On 22 February 2016 at 15:32, Luc-Eric Rousseau  wrote:
>>
>> The image library has a message that says "Cannot allocate xx bytes of
>> contiguous memory"
>> This might happen if you are using a lot of very large images.
>>
--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.


Re: si runs out of contiguous memory

2016-02-22 Thread Luc-Eric Rousseau
Also check if you have Fast Playback enabled, and disable it if so.
It's a  real memory hog
http://download.autodesk.com/global/docs/softimage2014/en_us/index.html?url=files/face_export_SavingandLoadingaFastPlaybackCacheFile.htm,topicNumber=d30e244326

On 22 February 2016 at 10:47, Luc-Eric Rousseau  wrote:
> It's possible the message is coming up with other types memory
> allocations as well, for example a big weight maps or other big
> arrays.
> Check if it's a a really big number. It's in bytes, I think, so you
> would device by 1024*1024 to get a number in megs.
> if the original number is greater than 2 bilions bytes, it would
> likely be a bug somewhere.
>
> On 22 February 2016 at 10:37, Matt Morris  wrote:
>> That's exactly the error message I'm getting, though I don't think I have
>> any images loaded - all my viewports are wireframe or shaded, and the
>> textures that are linked on the character are not linked up (remote job,
>> only have the model).
>>
>>
>> On 22 February 2016 at 15:32, Luc-Eric Rousseau  wrote:
>>>
>>> The image library has a message that says "Cannot allocate xx bytes of
>>> contiguous memory"
>>> This might happen if you are using a lot of very large images.
>>>
--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.



Re: si runs out of contiguous memory

2016-02-22 Thread Matt Morris
That's exactly the error message I'm getting, though I don't think I have
any images loaded - all my viewports are wireframe or shaded, and the
textures that are linked on the character are not linked up (remote job,
only have the model).


On 22 February 2016 at 15:32, Luc-Eric Rousseau <luceri...@gmail.com> wrote:

> The image library has a message that says "Cannot allocate xx bytes of
> contiguous memory"
> This might happen if you are using a lot of very large images.
>
> On 22 February 2016 at 10:16, Matt Morris <matt...@gmail.com> wrote:
> > I was thinking it must be a leak of some sort. Running win 7 64, an i7
> > 5930K, 32Gb ram, titan X. No issues with large scenes with billions of
> > polys. But a cartoony character that's not very high res, with only
> envelope
> > and shapes on is running out of memory. Wierd.
> >
> > I'm using the shape manager to model each shape in turn, generally
> switch to
> > different shape or anim tab to check it which bakes the move components
> into
> > the shape, so I don't see how its using up 32Gb..
> >
> > On 22 February 2016 at 15:07, Sven Constable <sixsi_l...@imagefront.de>
> > wrote:
> >>
> >> I think the "contiguous memory problem" can happen with 32bit as well as
> >> 64bit systems. Even if you have plenty of ram. Let's say you have 2 GB
> of
> >> free memory and  the application needs to allocate only 500megs of ram,
> it
> >> can fail because the 1GB is of small chunks and all of these chunks are
> >> under 500MB. The more applications or memory intensive tasks are
> running and
> >> the longer you work with them, the more "fragmented" the memory will
> become.
> >> It can help to restart the machine and use only the programs  you
> absolutely
> >> need. Perhaps more RAM can help to encounter the problem later, but I
> don't
> >> think it will solve it entirely.
> >>
> >> Haven’t seen this for quite some time.
> >>
> >>
> >>
> >> From: softimage-boun...@listproc.autodesk.com
> >> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of
> >> pete...@skynet.be
> >> Sent: Monday, February 22, 2016 3:23 PM
> >> To: softimage@listproc.autodesk.com
> >> Subject: Re: si runs out of contiguous memory
> >>
> >>
> >>
> >> hm, haven’t those words since the legacy particle system and 32bit.
> >>
> >> I understand this as ‘running out of ram’ (does task manager agree?)
> >>
> >>
> >>
> >> are you freezing the shapes?
> >>
> >> lots of dense geo, with lots of operations in the stack – sounds like
> >> you’ll eat up resources eventually.
> >>
> >>
> >>
> >> From: Matt Morris
> >>
> >> Sent: Monday, February 22, 2016 2:03 PM
> >>
> >> To: softimage@listproc.autodesk.com
> >>
> >> Subject: si runs out of contiguous memory
> >>
> >>
> >>
> >> Hi list,
> >>
> >>
> >>
> >> I've been modelling a lot of shapes in 2015 r2, and have been getting
> >> numerous crashes after a certain amount of work, where si seems to run
> out
> >> of memory with the above error. Particularly if I'm using proportional
> >> modelling and symmetry in the shape manager window. Definitely running
> >> slowly as well.
> >>
> >>
> >>
> >> I thought it might be to do with ice trees on other meshes referencing
> >> this one, but having deleted all refs and any ice trees on the geo, it
> still
> >> happens.
> >>
> >>
> >>
> >> Is anyone else seeing anything similar? Not sure whether its 2015
> related
> >> but I can't remember having anything like this much trouble in 2014 sp2.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >>
> >> www.matinai.com
> >>
> >> 
> >>
> >> --
> >> Softimage Mailing List.
> >> To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com
> >> with "unsubscribe" in the subject, and reply to confirm.
> >>
> >>
> >> --
> >> Softimage Mailing List.
> >> To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com
> >> with "unsubscribe" in the subject, and reply to confirm.
> >
> >
> >
> >
> > --
> > www.matinai.com
> >
> > --
> > Softimage Mailing List.
> > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com
> with
> > "unsubscribe" in the subject, and reply to confirm.
>
> --
> Softimage Mailing List.
> To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com
> with "unsubscribe" in the subject, and reply to confirm.
>



-- 
www.matinai.com
--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.

Re: si runs out of contiguous memory

2016-02-22 Thread Luc-Eric Rousseau
The image library has a message that says "Cannot allocate xx bytes of
contiguous memory"
This might happen if you are using a lot of very large images.

On 22 February 2016 at 10:16, Matt Morris <matt...@gmail.com> wrote:
> I was thinking it must be a leak of some sort. Running win 7 64, an i7
> 5930K, 32Gb ram, titan X. No issues with large scenes with billions of
> polys. But a cartoony character that's not very high res, with only envelope
> and shapes on is running out of memory. Wierd.
>
> I'm using the shape manager to model each shape in turn, generally switch to
> different shape or anim tab to check it which bakes the move components into
> the shape, so I don't see how its using up 32Gb..
>
> On 22 February 2016 at 15:07, Sven Constable <sixsi_l...@imagefront.de>
> wrote:
>>
>> I think the "contiguous memory problem" can happen with 32bit as well as
>> 64bit systems. Even if you have plenty of ram. Let's say you have 2 GB of
>> free memory and  the application needs to allocate only 500megs of ram, it
>> can fail because the 1GB is of small chunks and all of these chunks are
>> under 500MB. The more applications or memory intensive tasks are running and
>> the longer you work with them, the more "fragmented" the memory will become.
>> It can help to restart the machine and use only the programs  you absolutely
>> need. Perhaps more RAM can help to encounter the problem later, but I don't
>> think it will solve it entirely.
>>
>> Haven’t seen this for quite some time.
>>
>>
>>
>> From: softimage-boun...@listproc.autodesk.com
>> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of
>> pete...@skynet.be
>> Sent: Monday, February 22, 2016 3:23 PM
>> To: softimage@listproc.autodesk.com
>> Subject: Re: si runs out of contiguous memory
>>
>>
>>
>> hm, haven’t those words since the legacy particle system and 32bit.
>>
>> I understand this as ‘running out of ram’ (does task manager agree?)
>>
>>
>>
>> are you freezing the shapes?
>>
>> lots of dense geo, with lots of operations in the stack – sounds like
>> you’ll eat up resources eventually.
>>
>>
>>
>> From: Matt Morris
>>
>> Sent: Monday, February 22, 2016 2:03 PM
>>
>> To: softimage@listproc.autodesk.com
>>
>> Subject: si runs out of contiguous memory
>>
>>
>>
>> Hi list,
>>
>>
>>
>> I've been modelling a lot of shapes in 2015 r2, and have been getting
>> numerous crashes after a certain amount of work, where si seems to run out
>> of memory with the above error. Particularly if I'm using proportional
>> modelling and symmetry in the shape manager window. Definitely running
>> slowly as well.
>>
>>
>>
>> I thought it might be to do with ice trees on other meshes referencing
>> this one, but having deleted all refs and any ice trees on the geo, it still
>> happens.
>>
>>
>>
>> Is anyone else seeing anything similar? Not sure whether its 2015 related
>> but I can't remember having anything like this much trouble in 2014 sp2.
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> www.matinai.com
>>
>> 
>>
>> --
>> Softimage Mailing List.
>> To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com
>> with "unsubscribe" in the subject, and reply to confirm.
>>
>>
>> --
>> Softimage Mailing List.
>> To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com
>> with "unsubscribe" in the subject, and reply to confirm.
>
>
>
>
> --
> www.matinai.com
>
> --
> Softimage Mailing List.
> To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with
> "unsubscribe" in the subject, and reply to confirm.

--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.

Re: si runs out of contiguous memory

2016-02-22 Thread Matt Morris
I was thinking it must be a leak of some sort. Running win 7 64, an i7
5930K, 32Gb ram, titan X. No issues with large scenes with billions of
polys. But a cartoony character that's not very high res, with only
envelope and shapes on is running out of memory. Wierd.

I'm using the shape manager to model each shape in turn, generally switch
to different shape or anim tab to check it which bakes the move components
into the shape, so I don't see how its using up 32Gb..

On 22 February 2016 at 15:07, Sven Constable <sixsi_l...@imagefront.de>
wrote:

> I think the "contiguous memory problem" can happen with 32bit as well as
> 64bit systems. Even if you have plenty of ram. Let's say you have 2 GB of
> free memory and  the application needs to allocate only 500megs of ram, it
> can fail because the 1GB is of small chunks and all of these chunks are
> under 500MB. The more applications or memory intensive tasks are running
> and the longer you work with them, the more "fragmented" the memory will
> become. It can help to restart the machine and use only the programs  you
> absolutely need. Perhaps more RAM can help to encounter the problem later,
> but I don't think it will solve it entirely.
>
> Haven’t seen this for quite some time.
>
>
>
> *From:* softimage-boun...@listproc.autodesk.com [mailto:
> softimage-boun...@listproc.autodesk.com] *On Behalf Of *pete...@skynet.be
> *Sent:* Monday, February 22, 2016 3:23 PM
> *To:* softimage@listproc.autodesk.com
> *Subject:* Re: si runs out of contiguous memory
>
>
>
> hm, haven’t those words since the legacy particle system and 32bit.
>
> I understand this as ‘running out of ram’ (does task manager agree?)
>
>
>
> are you freezing the shapes?
>
> lots of dense geo, with lots of operations in the stack – sounds like
> you’ll eat up resources eventually.
>
>
>
> *From:* Matt Morris <matt...@gmail.com>
>
> *Sent:* Monday, February 22, 2016 2:03 PM
>
> *To:* softimage@listproc.autodesk.com
>
> *Subject:* si runs out of contiguous memory
>
>
>
> Hi list,
>
>
>
> I've been modelling a lot of shapes in 2015 r2, and have been getting
> numerous crashes after a certain amount of work, where si seems to run out
> of memory with the above error. Particularly if I'm using proportional
> modelling and symmetry in the shape manager window. Definitely running
> slowly as well.
>
>
>
> I thought it might be to do with ice trees on other meshes referencing
> this one, but having deleted all refs and any ice trees on the geo, it
> still happens.
>
>
>
> Is anyone else seeing anything similar? Not sure whether its 2015 related
> but I can't remember having anything like this much trouble in 2014 sp2.
>
>
>
>
>
>
>
> --
>
> www.matinai.com
> --
>
> --
> Softimage Mailing List.
> To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com
> with "unsubscribe" in the subject, and reply to confirm.
>
> --
> Softimage Mailing List.
> To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com
> with "unsubscribe" in the subject, and reply to confirm.
>



-- 
www.matinai.com
--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.

Re: si runs out of contiguous memory

2016-02-22 Thread peter_b
hm, haven’t those words since the legacy particle system and 32bit.
I understand this as ‘running out of ram’ (does task manager agree?)

are you freezing the shapes?
lots of dense geo, with lots of operations in the stack – sounds like you’ll 
eat up resources eventually.

From: Matt Morris 
Sent: Monday, February 22, 2016 2:03 PM
To: softimage@listproc.autodesk.com 
Subject: si runs out of contiguous memory

Hi list, 

I've been modelling a lot of shapes in 2015 r2, and have been getting numerous 
crashes after a certain amount of work, where si seems to run out of memory 
with the above error. Particularly if I'm using proportional modelling and 
symmetry in the shape manager window. Definitely running slowly as well.

I thought it might be to do with ice trees on other meshes referencing this 
one, but having deleted all refs and any ice trees on the geo, it still happens.

Is anyone else seeing anything similar? Not sure whether its 2015 related but I 
can't remember having anything like this much trouble in 2014 sp2.



-- 

www.matinai.com



--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.

si runs out of contiguous memory

2016-02-22 Thread Matt Morris
Hi list,

I've been modelling a lot of shapes in 2015 r2, and have been getting
numerous crashes after a certain amount of work, where si seems to run out
of memory with the above error. Particularly if I'm using proportional
modelling and symmetry in the shape manager window. Definitely running
slowly as well.

I thought it might be to do with ice trees on other meshes referencing this
one, but having deleted all refs and any ice trees on the geo, it still
happens.

Is anyone else seeing anything similar? Not sure whether its 2015 related
but I can't remember having anything like this much trouble in 2014 sp2.



-- 
www.matinai.com
--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.