Program Hangs When Changing Category

[ChrisB]

After entering abput 12 mocies into a db using the imdb script I found several are incorrectly categorised, while changing the category the program hangs and becomed non responsive, I have to close it from the task manager. This is repeatable but doesnt always happen on the same film and may happen after any number of changes e.g. the 1st, 4th, 7th change!
I am running Win2k sp4, 512 ram
thanks
Chris

[antp]

I never had the problem and you're the first to report it.
If happens at the moment you select a value from a drop-down field?

[ChrisB]

Dont worry ... It might be some strange mouse interaction (I have vbscroll loaded) or clash with some anti spyware program etc. I have switched to my XP Home machine and it works fine. Because that machine is a development machine its dlls can be in an 'uncertain state'.
Nice program, works well now.
Chris

[Szym]

I never had the problem and you're the first to report it.
If happens at the moment you select a value from a drop-down field?

Then I'm the second case.
I've just upgraded to v.3.5 (because I had some problems with scripts -IMDB).
Program hanged after I'd chosen source server for a movie.
I had to use "end process" in XP manager. My data remained intact, fortunately.

[antp]

What do you mean by "source server"? In script importation? That's not really the same case than what ChrisB described.
Which script cause that? All?

[Proteus]

I wonder if this is related to my problem. I too experience hangs shortly after using the imdb script.

[driko]

I too have had this happen several times in a row now, after changing media types for movies already entered. Up to this point, the program has been stable, but now after changing the media type for some random number of movies, the program hangs up and I have to end it via the task manager.

I'm running Windows XP Home, 1GB Ram. Any ideas?


Thanks...

[antp]

Some people have similar problems, but I can't reproduce it on my PC. It seems that all are using a recent AMD processor, but the problem does not happen to my old 1.2 GHz AMD. I guess it is related to either the 64 bits AMD or a chipset of the motherboards.
I tried remote debug few days ago but I could not localize where in the code it happens Maybe it's even not in my own code but in a library that I use.
Some time ago there was a problem with Hyperthreading Pentium 4, with version 3.4.2 of the program.