by dastriebel » Sat Nov 15, 2003 7:42 am
My Environment:
- Windows XP, Professional, German, Service Pack 1, all Updates installed.
- MediaMonkey 2.1 (Build: 1.596)
Steps to reproduce the bug (not everytime):
1. Start MediaMonkey
2. Start ripping a CD
3. Go to an existing database entry
4. Start playing a song (enter-key in the overview)
5. Change the Rating off a song in the overview
6. Try playing another song (enter-key in the overview)
==> Access violation at adress 00000000. Read address 00000000.
7. Klick OK
8. Try playing another song (enter-key in the overview)
==> Access violation at adress 00000005. Read address 00000005.
Sometimes stepp 5 and 6 has to be repeated
Other Messages i got with thit procedure:
- Access violation at address 0061007 in module 'MediaMonkey.exe'. Write of address 10C7C0AD.
- Access violation at adress 01DC4CC2. Read address FFFFFFFF.
- Access violation at address 1C40506F in module 'amstream.dll'. Read of address 03B89960.
I know my information is not very specific, but if i find a way to really reproduce the bug i will post it her.
My Environment:
- Windows XP, Professional, German, Service Pack 1, all Updates installed.
- MediaMonkey 2.1 (Build: 1.596)
Steps to reproduce the bug (not everytime):
1. Start MediaMonkey
2. Start ripping a CD
3. Go to an existing database entry
4. Start playing a song (enter-key in the overview)
5. Change the Rating off a song in the overview
6. Try playing another song (enter-key in the overview)
==> Access violation at adress 00000000. Read address 00000000.
7. Klick OK
8. Try playing another song (enter-key in the overview)
==> Access violation at adress 00000005. Read address 00000005.
Sometimes stepp 5 and 6 has to be repeated
Other Messages i got with thit procedure:
- Access violation at address 0061007 in module 'MediaMonkey.exe'. Write of address 10C7C0AD.
- Access violation at adress 01DC4CC2. Read address FFFFFFFF.
- Access violation at address 1C40506F in module 'amstream.dll'. Read of address 03B89960.
I know my information is not very specific, but if i find a way to really reproduce the bug i will post it her.