bugs 2005-05-05 - By kim aldis
Back
Send the xsicab anyway, it sends a history of crashes so it'll catch all
those priors.
> -- --Original Message-- --
> From: owner-xsi@(protected)
> [mailto:owner-xsi@(protected)] On Behalf Of Matt Hollingsworth
> Sent: 04 May 2005 23:39
> To: XSI@(protected)
> Subject: Re: bugs
>
> Hey,
>
> Of course, now it won't crash. XSI wrote and wants me to
> send them the CAB, and it won't crash when I want it to.
> Alway crashes when I _don't want it to, though, so I gotta trick it!
>
> ;-)
>
> Anyway, I am indeed on dual monitor. I have two copies of
> XSI open, but these same exact problems happen to the guy
> next to me, who never works with two copies open. Other
> thant those, the only things I have open are Thunderbird,
> AIM, Firefox and the task manager, none of which is taking
> very many resources.
>
> Yeah, I reboot two or three times a day usually. I always
> reboot when I arrive at work first off, then usually after a
> crash, though not every time or I'd spend my entire day rebooting.
>
> Same res on both monitors. Yes, very heavy workgroups, but
> can't do anything about that.
>
> Thanks for all the ideas everyone.
>
> -M
>
> 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
> >
> >
> >
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following
> text in body:
> unsubscribe xsi
>
>
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
