Page 3 of 4

Beta 1.0.122 holds .wma file handles open

PostPosted: September 30th, 2009, 1:55 am
by davydm
Good day

I just updated to the 122 beta and noticed that Xion is keeping handles to .wma files open even when not playing. Yes, I know, .wma is evil and should be purged -- some have snuck into my 120 gig collection ):

I noticed this when trying to eject the removable drive upon which is my music -- I couldn't. I used the Unlocker utility to find that Xion was holding open handles to many many .wma files -- even though I hadn't played them. I assume that the files were opened at the load of the playlist and just not properly closed.

This bug, apart from making it difficult to remove a removable drive Xion was playing from, is probably causing an unwanted use of memory.

Re: Beta 1.0.122 holds .wma file handles open

PostPosted: September 30th, 2009, 9:17 am
by Cliff Cawley
davydm Wrote:Good day

I just updated to the 122 beta and noticed that Xion is keeping handles to .wma files open even when not playing. Yes, I know, .wma is evil and should be purged -- some have snuck into my 120 gig collection ):

I noticed this when trying to eject the removable drive upon which is my music -- I couldn't. I used the Unlocker utility to find that Xion was holding open handles to many many .wma files -- even though I hadn't played them. I assume that the files were opened at the load of the playlist and just not properly closed.

This bug, apart from making it difficult to remove a removable drive Xion was playing from, is probably causing an unwanted use of memory.


Thanks for the report davydm, I'll have to see if I can reproduce this and get it fixed

Cliff :)

PostPosted: October 1st, 2009, 5:49 am
by krt16
Dont know if it is just me being dumb or something, but the crossfading on my player was active after I installed the build 122. I do not like crossfading so I went to the settings to turn it off, and noticed that crossfading was not activated in the settings menu, but was active on the player. So I tried to activate it in the settings menu and it was deactivated then. So Crossfading (as it is at my comp) is active at the player when its not in the settings menu

PostPosted: October 4th, 2009, 4:14 am
by SLoB
Hahah, remembered the saving of tag info

Cannot save tag info on an m4a track, comes up with error file is in use
CAN save tag info on an mp3

not checked any other file types but I suspect there may be issues with other files?

PostPosted: October 4th, 2009, 9:56 pm
by logokas
My VC++ Runtime error has returned. I'm going to need the crash log-enabled build from you, Cliff, since it seems i'm the only one who gets this, and i have no idea how to reproduce.

PostPosted: October 5th, 2009, 9:10 pm
by Dilinger
logokas Wrote:My VC++ Runtime error has returned. I'm going to need the crash log-enabled build from you, Cliff, since it seems i'm the only one who gets this, and i have no idea how to reproduce.


Same problem ! Revert to build 121.
Windows 7 version = "6.1.7600.16385"

PostPosted: October 6th, 2009, 8:54 am
by logokas
So the problem is Win7 specific? Well, that explains why nobody else besides us techies have noticed this.

PostPosted: October 6th, 2009, 12:48 pm
by Cliff Cawley
logokas Wrote:So the problem is Win7 specific? Well, that explains why nobody else besides us techies have noticed this.


I develop Xion on Windows 7. Perhaps you should put that gun away logokas, you've used it too much lately :)

Can I have the exact error message? I doubt its related to the runtimes, more likely its just a crash.

Cliff :)

PostPosted: October 6th, 2009, 5:16 pm
by logokas
It's just the basic 'Has encountered fatal error' message. No error codes or crash dumps.

And i'm not on the gun, i don't have anything against 7 as an OS, just saying the whole Vista/7 quirks can be troublesome more often than not.

PostPosted: October 6th, 2009, 7:23 pm
by SLoB
I too will be moving to Win7 Pro very shortly, managed to evade Vista crap even though I had it since Oct 2006 (used it a few times in 3 years lol).
Win7 has to be the way forward, if they f**k it up this time then they are doomed.
Will still be keeping the XP hdd as standby tho lol ;)

PostPosted: October 7th, 2009, 12:54 am
by logokas
The bug suddenly happened during the stream, out of nowhere.

The exact error message is: Runtime Error! Abnormal Program Termination.

PostPosted: October 7th, 2009, 1:12 am
by SLoB
hmm logokas I know this doesn't help with your error but repeat that error in an Arnie voice ;)
And that's how I imagine it heheh ;) 2 verbose or not 2 verbose ;)

Check eventvwr, it might be able to shed a little more light on it

PostPosted: October 9th, 2009, 4:23 am
by OfficerMike07
krt16 Wrote:Dont know if it is just me being dumb or something, but the crossfading on my player was active after I installed the build 122. I do not like crossfading so I went to the settings to turn it off, and noticed that crossfading was not activated in the settings menu, but was active on the player. So I tried to activate it in the settings menu and it was deactivated then. So Crossfading (as it is at my comp) is active at the player when its not in the settings menu


Nah, you're not going crazy; I have this problem too. A simple workaround until it's fixed: enable crossfading, but with time set to 0.

PostPosted: October 9th, 2009, 6:45 am
by logokas
"Enabling" the crosshair disables it. Just a minor bug, really.

PostPosted: October 16th, 2009, 2:42 pm
by xonenine
I have found I can't close the equalizer/configure panel once I open it in 122.Am I the only one who is experiencing this?

It only seems to happen with some skins...

Also, I like the new playlist.thanks, :)