New External App: Netflix Viewer

[dhgb256]

I like this app, but I am almost ready to give up on it. The Database build program continually crashes. I have upgraded to the most recent build 2.9.1.0 and it still cannot complete a download. This is all that ever gets logged. Hope you can help. I have 2 PCs that it fails on in the same manner. Both run Windows 7 Ultimate 64 bit. I am in the US.

I think you are my first 64 bit user, might be some issue with that. To post your log files, you just need to click "Go Advanced" below the reply and then click "Manage Attachments" on the next screen below the reply. That will allow you to post files.

Neither of these logs shows any errors. What exactly happens during the crash? Does it hang, or is the program closing unexpectedly, or do you get a program crash report? Does it always happen during Step 1 of 2? If you can answer that for me, then i can put together a test build for you.

-DH

[dhgb256]

Your right. I had 2.9.0.5 and then after download and install from zip file "named" 2.9.1.0 the download/splash screen said 2.9.0.1. Checked the version and it was the wrong one in the zip.... Anyways... movies you will love causes a .net crash in 2.9.1.1.

That is what happens when I rush. I will get the 2.9.1.1 fixed tonight.

-DH

[dhgb256]

Shoot...spoke to soon. The builder seemed to go fine. But now when loading Viewer, it just sits there and says "LOADING, Please Wait". How long does it sit like this for?

*UPDATE*
Never mind, it finally came up with the list of movies.
Now all is good in the world.

Hi Marbles,

The ini file I put in the latest release has SGID=0, change this to SGID=307. That should fix the problem. Sorry about that, i keep forgetting about the canadian queue nonexistance. In the future, on new releases check the ini before loading the program to make sure that line isn't in there.

-DH

[cooper76]

I think you are my first 64 bit user, might be some issue with that. To post your log files, you just need to click "Go Advanced" below the reply and then click "Manage Attachments" on the next screen below the reply. That will allow you to post files.

Neither of these logs shows any errors. What exactly happens during the crash? Does it hang, or is the program closing unexpectedly, or do you get a program crash report? Does it always happen during Step 1 of 2? If you can answer that for me, then i can put together a test build for you.

-DH

Hi DH,

I'm another one of those Win7 64bit users and I'm having that crashing problem. It usually crashes around 30% on step 1 of 2, but I did get to 80% one time. I have attached the log files (one is from the Windows Event Logs) and a screenshot. Let me know if you need anymore info.

Thanks

[richt]

I think you are my first 64 bit user, might be some issue with that. To post your log files, you just need to click "Go Advanced" below the reply and then click "Manage Attachments" on the next screen below the reply. That will allow you to post files.

Neither of these logs shows any errors. What exactly happens during the crash? Does it hang, or is the program closing unexpectedly, or do you get a program crash report? Does it always happen during Step 1 of 2? If you can answer that for me, then i can put together a test build for you.

-DH

Here are all the log type files I can find. If there are others, let me know the names or name format and I'll look for them. BTW, I did update to 2.9.1.1 before collecting these files. I also included a screen shot of the error. It usually occurs in about the same spot, or close to it. It was working up until a month or so ago. Sorry that I cannot pinpoint at which build it stopped working, but I don't install all builds either so anything I tell you might not be accurate.

[dhgb256]

Hi DH,

I'm another one of those Win7 64bit users and I'm having that crashing problem. It usually crashes around 30% on step 1 of 2, but I did get to 80% one time. I have attached the log files (one is from the Windows Event Logs) and a screenshot. Let me know if you need anymore info.

Thanks

Since this is happening at two different spots for you and Richt, but in the same function, i am guessing i have an API call that is occasionally causing problems. Keep an eye out for a debug build that I will post tonight. That will help me narrow down the problem.

-DH

[dhgb256]

Here are all the log type files I can find. If there are others, let me know the names or name format and I'll look for them. BTW, I did update to 2.9.1.1 before collecting these files. I also included a screen shot of the error. It usually occurs in about the same spot, or close to it. It was working up until a month or so ago. Sorry that I cannot pinpoint at which build it stopped working, but I don't install all builds either so anything I tell you might not be accurate.

I'll send a test build to you and cooper tonight (see message #811).

-DH

[dhgb256]

Since this is happening at two different spots for you and Richt, but in the same function, i am guessing i have an API call that is occasionally causing problems. Keep an eye out for a debug build that I will post tonight. That will help me narrow down the problem.

-DH

OK, please try this version.

Long winded explanation :

Knowing it is an IO error, I was able to find the likely cause pretty quickly. Apparently it is only exposed in the 64 bit version because you execute the code faster. I was stupidly releasing a hold variable before closing a file, instead of after. Apparently the 64 bit version is trying to open the file as soon as I release the variable and the x86 version takes long enough that the file is closed. I am pretty sure that caused the error. Let me know if this works.

-DH

[Mike S]

Tried the Que only approaach and it run the database builder anyway and hangs.

[dhgb256]

Tried the Que only approaach and it run the database builder anyway and hangs.

Hi Mike,

I ahve a few questions for you, so i can try and get this fixed:

Are you having the same problem as cooper and richt for the full database build?
Are you in the US or in canada?
Do you have any log files that you can post?
Which program version are you running?

The queue only approach does run the builder, but only for your queue. Total build time should be about 20 seconds - 2 minutes.

-DH