Fishy
Senior Member
Posts: 960
Registered: 10-19-2003
Location: Norway, Trondheim
Member Is Offline
|
posted on 9-17-2011 at 12:10 AM
|
|
|
Unstable ejukebox
I get these crashes by ejukebox from the latest versions.
Problem signature:
Problem Event Name: APPCRASH
Application Name: ejukebox.exe
Application Version: 5.67.0.0
Application Timestamp: 4e100af6
Fault Module Name: StackHash_5485
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 850f57c0
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1044
Additional Information 1: 5485
Additional Information 2: 5485a9a152dbc667bb57c90ab02027c0
Additional Information 3: e0cb
Additional Information 4: e0cbc728c501e9411806f8b5add7ea84
Any ideas? Usually happens when I move the mouse into the corners of the program (e.g. towards the X to close the program above the albumlist). I have
tried to disable the mouse features recently added, but still the same.
|
|
Audiosoft
|
posted on 9-17-2011 at 12:15 AM
|
|
|
Fishy what skin is this with? are you using a searchbuttonhi.png in your skin?
i remember it crashing sometimes when i moused over the searchbuttonhi.png. i am not sure if that is still a problem...most skins use jpg for the
searchbox or just a searchbutton.png.
Audiosoft
|
|
Fishy
Senior Member
Posts: 960
Registered: 10-19-2003
Location: Norway, Trondheim
Member Is Offline
|
posted on 9-23-2011 at 11:04 PM
|
|
|
Thanks Audiosoft. A reinstall seems to have aided things. Ejukebox was suddenly asking for a number of vb.files that I have never heard of and also
crashed at random. Deletion of the ejukebox directory and reinstallation seems, however, to have fixed the problems. I am currently undergoing my
first rebuild in ages, and it hits me that I probably should do this type of housekeeping more often (i.e. the scheudle feature I nagged over a while
ago will now be put to good use). Thanks
-----------
Fishy
|
|
peleus
Junior Member
Posts: 50
Registered: 1-13-2013
Member Is Offline
|
posted on 1-19-2013 at 06:41 PM
|
|
|
I guess this was also fixed in v5.23.
|
|