| Author |
Message |
| Registered: March 13, 2007 | | Posts: 793 |
| | Posted: | | | | It's the third time I get this error:  So far, it has always happened doing the exact same thing, which adding the <![epgfn=LostS1]> tag in the notes for the Episode Guide loader. When it happens, I've just used a quick macro from my G15 keyboard, which automatically fills in "<![epgfn=]>" and moves the cursor in position right after the = sign. I then hit CTRL-V to paste the name of the serie I'm working, for example, right now I was doing Red Dwarf, so it would add "RedDwarfS". So at this point, I have "<![epgfn=RedDwarfS]>" filled in, with the cursor between the S and ]. I then hit "5" on the numpad (I was doing season 5 when the error happened) and that's when the access violation appears. I've not clicked OK, and I haven't hit ENTER (as it would just add a line return to the notes). It had worked fine for Seasons 1, 2, 3 and 4.. It then crashed on Season 5. When this access violation arrives, it gets stuck into a loop and I have to kill the process from Task Manager. Forgot to mention I'm using DVD Profiler 3.0.3 b1136 on Windows XP Professional SP2 | | | | Last edited: by RossRoy |
|
| Registered: March 13, 2007 | Reputation:  |  Posts: 1,109 |
| | Posted: | | | | Today I keep getting "Access Violation at address 00A95E03 in module 'dvdpro.exe'. Read of address 0000005F." after editing anything within a profile and clicking "OK" to save. It happens everytime!
I can go into edit mode and and not make any changes, and the access error won't appear.
But if I go in and make any field changes, it will.
RossRoy, are you still getting this access violation?
Does it only happen you edit notes or any other fields within the profile? |
|
| Registered: March 13, 2007 | | Posts: 793 |
| | Posted: | | | | It's an intermittent problem. Sometimes I'll get it, sometimes I won't. I've gotten it mostly from editing the notes, but I was adding some new manual additions (I didn't have the UPC at the time) and it crashed at one point when I clicked ok to confirm the changes.
But it's really random. I really can't find any common scenario to trigger it unfortunately.
I didn't know there was a debug log that was kept in the Application Data folder, so I haven't checked it when it crashed. I'm now "hoping" (not really) it will crash again so I can take a look at the file and maybe see what's happening. | | | | Last edited: by RossRoy |
|
| Registered: March 14, 2007 | | Posts: 223 |
| | Posted: | | | | This is happening to me today as well. I was changing some local SRPs to zero (they were part of boxsets) and each one I changed gave me the access violation. I also edited an overview and got the error as well. Here is my debug log....but I have no idea what it means. 2007/06/07 9:42:55 AM: Application Startup. 2007/06/07 9:42:55 AM: Checking AppInit 2007/06/07 9:42:55 AM: AppInit False 2007/06/07 9:42:55 AM: Check for success 2007/06/07 9:42:55 AM: Freeing AppRegistry 2007/06/07 9:42:55 AM: AppRegistry Free 2007/06/07 9:42:55 AM: Checking additional params 2007/06/07 9:42:55 AM: Creating splash 2007/06/07 9:42:55 AM: Splash shown. Application.Initialize processing 2007/06/07 9:42:55 AM: Creating Main form 2007/06/07 9:42:56 AM: Main form create starting 2007/06/07 9:42:56 AM: Forcing directories 2007/06/07 9:42:56 AM: Initializing threads 2007/06/07 9:42:56 AM: Validating registration 2007/06/07 9:42:56 AM: Loading locality list 2007/06/07 9:42:56 AM: Reading options from registy 2007/06/07 9:42:56 AM: Translation intializing 2007/06/07 9:42:56 AM: Creating DataMod 2007/06/07 9:43:01 AM: Creating additional forms 2007/06/07 9:43:01 AM: Retranslating Main form 2007/06/07 9:43:01 AM: Initializing plugins 2007/06/07 9:43:04 AM: Main form showing 2007/06/07 9:43:18 AM: Main form activating 2007/06/07 9:43:20 AM: Freeing splash 2007/06/07 9:43:20 AM: Running Application 2007/06/07 10:06:24 AM: Application Shutdown Complete. 2007/06/07 10:06:24 AM: frmMain Destroy Start 2007/06/07 10:06:25 AM: frmMain Destroy End  |
|
| Registered: March 13, 2007 |  Posts: 2,692 |
| | Posted: | | | | it seems to happen mostly when the screen needs to refresh. I.e. after applying updates.
I'm hoping that Ken hasn't made any update recently because he was trying to fix this - he has mentioned that he had managed to duplicate the problem in the beta test forum | | | | Paul |
|
| Registered: March 10, 2007 |  Posts: 4,282 |
| | Posted: | | | | We've identified and corrected an error that can cause this. If you have the disc location column shown in the collection list, try turning it off and see if the error stops. | | | | Invelos Software, Inc. Representative |
|
| Registered: March 13, 2007 | | Posts: 793 |
| | Posted: | | | | Quoting Ken Cole: Quote:
We've identified and corrected an error that can cause this. If you have the disc location column shown in the collection list, try turning it off and see if the error stops. I don't have the disc location showing in the collection list, as I don't use this field at all. The only data I have showing in the collection list will either the the covers (as I mostly work in thumbnails mode), or, if I happen to be working with a text list, then the columns showing will be only Title and Collection number. |
|
| Registered: March 13, 2007 | | Posts: 2,692 |
| | Posted: | | | | Quoting Ken Cole: Quote:
We've identified and corrected an error that can cause this. If you have the disc location column shown in the collection list, try turning it off and see if the error stops. I'll try this. | | | | Paul |
|
| Registered: March 13, 2007 | | Reputation: | | Posts: 1,109 |
| | Posted: | | | | Quoting RossRoy: Quote:
Quoting Ken Cole:
Quote:
We've identified and corrected an error that can cause this. If you have the disc location column shown in the collection list, try turning it off and see if the error stops.
I don't have the disc location showing in the collection list, as I don't use this field at all. The only data I have showing in the collection list will either the the covers (as I mostly work in thumbnails mode), or, if I happen to be working with a text list, then the columns showing will be only Title and Collection number. Try toggling the column on and then off. Does that help? |
|
| Registered: March 13, 2007 | | Posts: 793 |
| | Posted: | | | | Quoting Doombear: Quote:
Try toggling the column on and then off. Does that help? Didn't just change anything. I just added quite a few trailers in my notes field (see here), no crashes at all. I did some in text mode, and others in thumbnails mode.. nothing, no crashes. Hard to diagnose when you don't get the problem anymore |
|
| Registered: March 13, 2007 | | Reputation: | | Posts: 1,109 |
| | Posted: | | | | My Access Violations stopped happening too. Maybe good Ken changed something on the server side of things? |
|
| Registered: March 13, 2007 | | Posts: 2,692 |
| | Posted: | | | | Quoting Doombear: Quote:
Maybe good Ken changed something on the server side of things? how would that affect the desktop version? | | | | Paul |
|
| Registered: June 8, 2007 |  Posts: 58 |
| | Posted: | | | | Quoting Ken Cole: Quote:
We've identified and corrected an error that can cause this. If you have the disc location column shown in the collection list, try turning it off and see if the error stops. Just so you know: I've had the same Access Violation error occuring after almost every DVD I added to my collection. Removing the "Location" column from the left list of DVD profiler made the error go away indeed. I'm now looking forward to the next bugfix which will hopefully fix this bug as I *really* like to have that column back in view. |
|
| Registered: March 13, 2007 | | Posts: 2,692 |
| | Posted: | | | | Quoting Italo Disco: Quote:
Quoting Ken Cole:
Quote:
We've identified and corrected an error that can cause this. If you have the disc location column shown in the collection list, try turning it off and see if the error stops.
Just so you know: I've had the same Access Violation error occuring after almost every DVD I added to my collection. Removing the "Location" column from the left list of DVD profiler made the error go away indeed.
I'm in the same position - I haven't had any errors recently since I removed the location column. But I would also like it back.  | | | | Paul |
|
| Registered: May 31, 2007 | | Posts: 7 |
| | Posted: | | | |  I'm not using the location, but still have this error. Any ideas to resolve this? | | | | Last edited: by jochie |
|
| Registered: March 13, 2007 | | Posts: 793 |
| | Posted: | | | | Quoting HooGLaNDeR: Quote:
I'm not using the location, but still have this error. Any ideas to resolve this? Looks like I'm not alone in having this error, yet not using the location column. But to be fair, I still didn't get this error since my last post. |
|