 | | | bugs | bugs 2005-05-05 - By Brad Friedman
Back
thought I'd mention:
Holger said he had a similar issue on a workstation that ran maya a lot. Maya,
for a number of versions (I don't know if they ever really fixed this) was
notorious for leaking user objects and gdi objects. So thats a likely cause in
that case.
-brad
Luc-Eric Rousseau wrote:
>Crashes when opening windows or changing layout (which creates windows..) is
symptomatic of running out of resources under windows. Resources are memory
slots given to items such as menu handles and bitmaps. You're more prone to
get these problems if you run dual screen since you're probably using the space
and have twice as many windows.
>
>Perhaps you're running an application or task bar widget that leaks resources,
or takes a lot of them. For example, iTune is a pig in terms of Windows
resources (I'm sure they don't mind making windows look bad...), it takes as
many resources as XSI itself even in compact mode. There can be hungry
Explorer shell extentions as well. In the Task Manager, you can see how many
User Objects and GDI objects applications take.
>
>You could also be using a custom XSI layout that has too many views in it;
stack of views are very expensive and shouldn't dock large views like the
animation editor (which contains the dopesheet, expression editor, fcurve
editor and scene explorer)
>
>When all else fails rebooting the machine does clear out any resource leak
that might be lingering in the shell.
>
>
>
>
>>-- --Original Message-- --
>>From: owner-xsi@(protected)
>>[mailto:owner-xsi@(protected)]On Behalf
>>Of Matt Hollingsworth
>>Posted At: Wednesday, May 04, 2005 3:19 PM
>>Posted To: xsi
>>Conversation: bugs
>>Subject: bugs
>>
>>
>>Man, getting sick of some of these bugs in XSI. Does anybody know if
>>there is some huge open GL bug or something? I constantly
>>have crashes
>>when opening the freestanding windows for many things, but mostly the
>>animation mixer adn animation editor. In the shop here, it's
>>known that
>>you should either open those in a viewport or save before
>>trying to open
>>the freestanding window. That, and I often have crashes
>>when changing
>>my layout. And while copying and pasting is not causing
>>crashes, I sure
>>wish they'd fix it. There are many different areas where it
>>jsut does
>>not work properly. Also, to me, seems like XSI is particularly
>>sensitive to networks that are bogged down a bit. And, no,
>>this is not
>>isolated to my machine or my preferences. I also notice that when my
>>comps get a heavy node count that I am forced to use those little
>>navigation windows, and I really really HATE those things.
>>Would much
>>rather move around on my own. Same thing in the render tree.
>>
>>
>
>---
>Unsubscribe? Mail Majordomo@(protected) with the following text in body:
>unsubscribe xsi
>
>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859 (See http://ISO-8859.ora-code.com)-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
thought I'd mention:<br>
<br>
<pre wrap="">Holger said he had a similar issue on a workstation that ran maya
a lot. Maya, for a number of versions (I don't know if they ever really fixed
this) was notorious for leaking user objects and gdi objects. So thats a
likely cause in that case.</pre>
-brad<br>
<br>
Luc-Eric Rousseau wrote:
<blockquote
cite="midFA5227C034FA52469A8096BC4FD7AF7F010A7197@(protected)"
type="cite">
<pre wrap="">Crashes when opening windows or changing layout (which creates
windows..) is symptomatic of running out of resources under windows. Resources
are memory slots given to items such as menu handles and bitmaps. You're more
prone to get these problems if you run dual screen since you're probably using
the space and have twice as many windows.
Perhaps you're running an application or task bar widget that leaks resources,
or takes a lot of them. For example, iTune is a pig in terms of Windows
resources (I'm sure they don't mind making windows look bad...), it takes as
many resources as XSI itself even in compact mode. There can be hungry
Explorer shell extentions as well. In the Task Manager, you can see how many
User Objects and GDI objects applications take.
You could also be using a custom XSI layout that has too many views in it;
stack of views are very expensive and shouldn't dock large views like the
animation editor (which contains the dopesheet, expression editor, fcurve
editor and scene explorer)
When all else fails rebooting the machine does clear out any resource leak that
might be lingering in the shell.
</pre>
<blockquote type="cite">
<pre wrap="">-- --Original Message-- --
From: <a class="moz-txt-link-abbreviated" href="mailto:owner-xsi@(protected)"
>owner-xsi@(protected)</a>
[<a class="moz-txt-link-freetext" href="mailto:owner-xsi@(protected)">mailto
:owner-xsi@(protected)</a>]On Behalf
Of Matt Hollingsworth
Posted At: Wednesday, May 04, 2005 3:19 PM
Posted To: xsi
Conversation: bugs
Subject: bugs
Man, getting sick of some of these bugs in XSI. Does anybody know if
there is some huge open GL bug or something? I constantly
have crashes
when opening the freestanding windows for many things, but mostly the
animation mixer adn animation editor. In the shop here, it's
known that
you should either open those in a viewport or save before
trying to open
the freestanding window. That, and I often have crashes
when changing
my layout. And while copying and pasting is not causing
crashes, I sure
wish they'd fix it. There are many different areas where it
jsut does
not work properly. Also, to me, seems like XSI is particularly
sensitive to networks that are bogged down a bit. And, no,
this is not
isolated to my machine or my preferences. I also notice that when my
comps get a heavy node count that I am forced to use those little
navigation windows, and I really really HATE those things.
Would much
rather move around on my own. Same thing in the render tree.
</pre>
</blockquote>
<pre wrap=""><!---->
---
Unsubscribe? Mail <a class="moz-txt-link-abbreviated" href="mailto:Majordomo
@(protected)">Majordomo@(protected)</a> with the following text in body:
unsubscribe xsi
</pre>
</blockquote>
<br>
</body>
</html>
|
|
|