When I started using the beta, I expected the program to crash a lot, because that's what betas do.

Since the release went final, I have to report that I'm getting LOTS of crashes still, even when I'm doing nothing at all demanding.

I end up rebuilding the database a half dozen times a day just to restore some stability.

I can be in the collection list pane, pressing the down arrow key to move from one title to the next, and the program will crash all the way out (terminate its thread) without even stopping to send a report.

If I press up and down arrows quickly, it will start crashing sooner.

Using the mouse and clicking on icons in rapid succession will almost always generate a crash in a matter of seconds.

It's as if the program can't keep up with the screen refreshing and just barfs.

I get the same behavior in the "type a title to find" box.

Typing rapidly, or backspacing rapidly, will generate a crash in short order.

I end up with lots of "invalid blobs" like in this report:

Repair of table Thumbnails started at 2010-06-06 08:43:40
Invalid BLOB offset in BLOB file for physical record # 1, error fixed
Invalid BLOB offset in BLOB file for physical record # 696, error fixed
Invalid BLOB offset in BLOB file for physical record # 819, error fixed
Invalid BLOB offset in BLOB file for physical record # 914, error fixed
Invalid BLOB offset in BLOB file for physical record # 933, error fixed
Invalid BLOB offset in BLOB file for physical record # 964, error fixed
Invalid BLOB offset in BLOB file for physical record # 1195, error fixed
Repair of table Thumbnails completed at 2010-06-06 08:43:42
Repair of table Collection started at 2010-06-06 08:43:42
Repair of table Collection completed at 2010-06-06 08:43:45
Repair of table Aliases started at 2010-06-06 08:43:45
Repair of table Aliases completed at 2010-06-06 08:43:45
Repair of table BoxSets started at 2010-06-06 08:43:45
Repair of table BoxSets completed at 2010-06-06 08:43:45
Repair of table CreditsAssign started at 2010-06-06 08:43:45
Repair of table CreditsAssign completed at 2010-06-06 08:44:21
Repair of table ActorAssgn started at 2010-06-06 08:44:21
Repair of table ActorAssgn completed at 2010-06-06 08:45:22
Repair of table Actors started at 2010-06-06 08:45:22
Repair of table Actors completed at 2010-06-06 08:46:49
Repair of table DirectProduce started at 2010-06-06 08:46:49
Repair of table DirectProduce completed at 2010-06-06 08:46:59
Repair of table Discs started at 2010-06-06 08:46:59
Repair of table Discs completed at 2010-06-06 08:47:00
Repair of table Events started at 2010-06-06 08:47:00
Repair of table Events completed at 2010-06-06 08:47:00
Repair of table Retailers started at 2010-06-06 08:47:00
Repair of table Retailers completed at 2010-06-06 08:47:00
Repair of table Studios started at 2010-06-06 08:47:00
Repair of table Studios completed at 2010-06-06 08:47:00
Repair of table TagAssign started at 2010-06-06 08:47:00
Repair of table TagAssign completed at 2010-06-06 08:47:01
Repair of table Tags started at 2010-06-06 08:47:01
Repair of table Tags completed at 2010-06-06 08:47:01
Repair of table TimeStamps started at 2010-06-06 08:47:01
Repair of table TimeStamps completed at 2010-06-06 08:47:01
Repair of table Users started at 2010-06-06 08:47:01
Repair of table Users completed at 2010-06-06 08:47:01
Removed 0 unused crew member(s)
Removed 0 unused cast member(s)
Removed 0 unused studio(s)
Removed 0 unused retailer(s)

-----

Help!

One that I noticed is if you use a scroll wheel to quickly move through the collection. Sometimes it sticks and does not want to move forward (but can still go back). And indeed, sometimes the program freezes as if e.g. refreshing the thumbnails can't keep up.

If after numerous database repairs and you feel the virus program of yours is not responsible.. One trick I found out was to (get your windows version disc handy and) go into the start/run box and type in the letters  ' sfc /scannow ' . This windows fix program is designed especially for windows XP and I have found it made my machine  and its O/S run far better against certain applications and in this case it may make Profiller 3.6 run better. .
It certainly can't hurt and is maintenance free quality ..

If you continue to have issues then it sounds like it could be a hardware issue, RAM or bad sectors on your Harddrive.

Have you tried completely uninstalling and reinstalling DVDP?

Quoting leo1963:

Quote:
If you continue to have issues then it sounds like it could be a hardware issue, RAM or bad sectors on your Harddrive.

Thought of this too, but in this case other programs would be affected too.

@ lasitter: Which OS are you using?

Quoting leo1963:

Quote:
If you continue to have issues then it sounds like it could be a hardware issue, RAM or bad sectors on your Harddrive.

Have you tried completely uninstalling and reinstalling DVDP?

But if you notice there are more than just one or two havnig this problem. I guess it is possible that all of us suddenly developed HW problems. But as was mentioned by others, the only program that seems to be affected is DVDP. To clarify, I to have to restart DVDP a couple of times a day (it crashes, not hangs) and have to rebuild/repair the DB a couple of times a week.

I run Vista Home Premium 64 bit

I will look into my AVG, that is a good tip. I forgot about how difficult they can be w/ programs that constantly access.

P.S. AV realtime protection exclusion normally is set at the directory not at the programm accessing it. AT least that is how Norton is setup and also how Webroot Spysweeper was. Not sure about the other programs though.

Quoting Sparkss:

Quote:
I run Vista Home Premium 64 bit

I'm running DVDProfiler on Win7 HP 64bit (which are basically the same) with no problems at all.

Check your Windows system protocol (Within the sections "Critical" and "Errors") for DVDProfiler related errors.

This is a problem that has plagued me as well.

I moved from running DVD-Profiler v3.5 under Win-XP Pro x64 (64-bit) to running v.3.6.1 under Win7 Ultimate x64.  Under XP, DVD-Profiler v3.5 ran without any problems.  Under Win7, v3.6.1 has crashed extensively - by extensively, I mean 5 to 10-times in an hour - each time necessitating a repair operation before relaunching DVD-Profiler.  There was no obvious cause, and it would happen whether trying to move through the DVD listings, editing an entry, or ...., or.....

Finding some time last week, I investigated starting DVD-Profiler with the [ALT]-key held down and chose just to disable plug-ins.  In this manner I successfully edited a large number of entries and printed various reports without any murmur or sign of a crash or hesitation.  Following this I took out all plug-ins and then added them back one at a time testing each one extensively before testing the next one. 

Eventually the cause became obvious, it was the "Navigation History Plug-in (GoHistory)" from the sadly missed GoodGuy (Matthias Wolf).  With that removed, and all the others added back there's no problem.

Since then, I've edited nearly 100-entries and added 30 more with no hiccups.