frequent crashes

[TLDCompuFreak]

I purchased KoolMoves today, and have found it to crash very frequently. I find myself saving after every action because otherwise my work is likely to be lost. In less than a half hour of use it crashed at least 5 times. Windows says the program encountered an unhandled exception, and it is usually or perhaps always within a few seconds of deleting a frame. Is there perhaps a bug in the program that needs fixing?

[Bob Hartzell]

I am not aware of such a problem. The latest version (I assume you are using 4.1) was in beta test for considerable time. I am sure there was considerable frame deleting during those many weeks.

If you can create a scenerio that will produce such a crash, it will be very helpful. Also sending me the crash report will be helpful. There are about 4 different ways to delete a frame. Which way are you using?

In general, these may be causes of frequent crash problems --
- corrupted executable
- bad video card drivers
- general lack of system (graphic) resources
- running free RAM memory manager
- running application that adds skins to all toolbars
- running other large applications at the same time
- possibly incorrect settings when using a high-end video card
like FireGL or Intergraph Wildcat

[TLDCompuFreak]

I became busy with other things and didn't have time to check back for a response until now (sorry).

I am using version 4.1
I have been using the "-" (Delete Frame) button at the bottom of the interface (next to the "+" button that copies the current frame to the end).

When using Windows XP, after deleting a frame practically any action would cause a crash. I moved to another computer with Windows 98 and the problem seemed to stop, but now that I have tried to use it again it crashes fairly frequently. Deleting the current frame twice in a row seems to *always* crash it, no matter when, where, or in what animation.

Actions I have performed to cause a crash:
- Started Koolmoves
- Opened the file myhead6simp.fun (you can get it at http://www.greenblooded.com/temp/myhead6simp.fun)
- Used key frame scroller at bottom to go to key frame 20
- Clicked "-" button to delete frame
- Clicked "Yes" on messagebox that appeared
- Clicked "-" button to delete frame
- Clicked "Yes" on messagebox that appeared

At this point, Windows displayed a message saying that "This program has performed an illegal operation and will be shut down."

Clicking on the "Details>>" button, I got the following additional information (that I don't understand at all):

KOOLMOVES caused an invalid page fault in
module KOOLMOVES.EXE at 0167:006f994f.
Registers:
EAX=025b8968 CS=0167 EIP=006f994f EFLGS=00010202
EBX=00000001 SS=016f ESP=00b5f344 EBP=00b5f358
ECX=00000000 DS=016f ESI=00000000 FS=6117
EDX=00746f94 ES=016f EDI=025b8968 GS=0000
Bytes at CS:EIP:
8b 0e 8b 07 3b c8 74 39 83 79 f4 00 7d 0b 83 c1
Stack dump:
024cd400 00760b00 0040d296 025b8968 025b8940 00b5f3b0 0068a719 00000000 016f179f 024d5424 8382179f 179f0e3f 00000005 00000000 00036474 83d80e44

After clicking "Close" on this error message, Koolmoves was gone.

There are still other things that cause it to crash on my computer, but this is the only one I know how to duplicate.

[gorky2]

Hi, I tested your fun-file.No problem or crash under windows 2000 with koolmoves 4.1

Gorky

[FLASHPULSE]

I just tested your .FUN file as well. No crashes here. I have WIN XP (no updates). Nice animation.

[Bob Hartzell]

I am not aware of any current bugs which cause crashes (except for one possible rare situation)

I can only repeat what I said before as being possible crash problems. - corrupted executable
- bad video card drivers (happens more often than one would imagine)
- general lack of system (graphic) resources
- running free RAM memory manager
- running application that adds skins to all toolbars
- running other large applications at the same time
- possibly incorrect settings when using a high-end video card
like FireGL or Intergraph Wildcat

I assume that you have sufficient memory on your machine running XP. XP requires lots of memory.

[subvip7]

TLDCompuFreak...I'm not sure if this is your solutions but I had the exact same problem you did. I changed my monitor color depth to 16 bit and all the crashes vanished. Give it a try...can't hurt.

[necromanthus]

KM v4.0 and v4.1 were tested on:

Win98SE , WinME (my favorite) and WinXP-Pro (SP1)
Celeron 1.3GHz , P4/1.6 GHz and P4/2.53 GHz
128 , 256 and 512 MB RAM (SDR,DDR)
Radeon 7500 , GeForce4MX440 and GeForce4Ti4600

no problems at all !

[TLDCompuFreak]

Both of the computers I have problems on have 256MB of RAM. (One Win98 and one WinXP Home). I assume this is enough RAM, since I have no trouble with things that consume huge amounts of RAM (like photoshop-equivalent graphics software with several large multi-layer images, Microsoft Visual Studio, and 3D modelling/rendering software all running simultaneously).

My color depth is already 16 bit.

Thanks for your attempts to help, but I guess I just have to save extremely often and live with frequent crashes.

[necromanthus]

Originally posted by TLDCompuFreak
Thanks for your attempts to help, but I guess I just have to save extremely often and live with frequent crashes.

Don't be sad.
Let's try to solve your (systems) problem.
What videocards are you using and what resident programs are there ?

[Bob Hartzell]

(like photoshop-equivalent graphics software with several large multi-layer images, Microsoft Visual Studio, and 3D modelling/rendering software all running simultaneously).

-> Are all these running simultaneously? Close them down and see if the problem goes away. Running out of graphic resources often occurs before running out of memory. If all of these monster programs are running simultaneously, 256K memory is probably not enough.

[Fingermonkey]

The problem could also be something simple like making sure your anti virus software is disabled and all other windows are closed when you install KM. These things can corrupt registry files when installing an application, causing the application to crash.

[necromanthus]

Originally posted by Bob Hartzell
(like photoshop-equivalent graphics software with several large multi-layer images, Microsoft Visual Studio, and 3D modelling/rendering software all running simultaneously).

-> Are all these running simultaneously? Close them down and see if the problem goes away. Running out of graphic resources often occurs before running out of memory. If all of these monster programs are running simultaneously, 256K memory is probably not enough.

Indeed,
3DSMax ,Maya ,SoftImage ,etc are memory killers.
One of them is enough to "kill" 256 MB of RAM.
Also,all resident programs are "troubles generators".