[AOM 0.5.1.219] Error when updating mylist

Bug reports for an official AniDB Client go here

Moderators: AniDB, AniDB API

Locked
lamer_de

[AOM 0.5.1.219] Error when updating mylist

Post by lamer_de »

Well, at least I guess my AOM version is 0.5.1.219, because there is not a single hint which version I have when the program is running (hint: Make a version popup box under help), but the file version reports it back as that, so I guess it's te right version number.

Code: Select all

[30.08.2004 10:53:52] - Executing new AniDB command.
[30.08.2004 10:53:53] - Removing obsolete entries.
[30.08.2004 10:53:53] - Failed to update rmt:anime - 2434! The error message was: Access violation at address 006398A0 in module 'AOM.exe'. Read of address 00000014
[30.08.2004 10:53:53] - Executing new AniDB command.
[30.08.2004 10:53:53] - Converting and saving new mylist data.
[30.08.2004 10:53:53] - Loading mylist data...
[30.08.2004 10:53:54] - Failed to update mylist - 2434! The error message was: Access violation at address 006398A0 in module 'AOM.exe'. Read of address 00000014
[30.08.2004 10:53:54] - Executing new AniDB command.
[30.08.2004 10:53:54] - Removing obsolete entries.
[30.08.2004 10:53:54] - Obsolete entries removed after 0 milliseconds.
[30.08.2004 10:53:56] - Connection to AniDB successfully terminated. All queued tasks completed.
AOM keeps working as far as I can judge it, but I only use it for simple operations on my mylist.

CU,
lamer_de
Guest

Post by Guest »

or maybe not:

Image

Randomly happens when I want to access the Mylist tab. Sorry, can't edit posts as guest and I don't see the necessity to register here. Reach me on ar or ircif you need more feedback.

CU,
lamer_de
PetriW
AniDB Staff
Posts: 1522
Joined: Sat May 24, 2003 2:34 pm

Post by PetriW »

You can right click on the exe and select properties to get it's current version.

About the bug, the access violations are kinda hard to trace and won't occur in the same way in 0.6 anyway so not gonna dig deep into them.

Regarding the second error it's known and caused by a component I use, it's one of those "should not happen" errors and I'll just trap it in 0.6 so it'll go away.
Locked