oh guys, i don't know what to do. at times this new version looked like it
was doing okay, it even seemed that it solved some old issues (and it did,
in a way), but it's really mysterious and full of surprise bugs. memory
leaks, crashes, not doing what told to do, and out of a sudden pretending to
and actually working normally.
as i understand this new version was built some other way than the old ones,
using some new 'easier' pathway for cross compiling. maybe that makes it a
disaster, i don't know.
i have two options now: go back to the last 32bit version when it was kind
of predictable and leak free, or try to build a new 64bit one myself.
also, what about cygwin? maybe a cygwin version would be less work for
developers and then at least it would have the same bugs as linux version?
or should i try cygwin path myself?
are there any runtimes or other external things in windows that it depends
on? i dont' know where to start, even the debugger is broken in that thing,
it's a complete mess that's working by a miracle... and sometimes i find it
having eaten 24GB of RAM, or crashed out of the blue, not decoding things it
apparently supports, even playing playlists at wrong times! [the config
hasn't changed for years, just some expressions were adapted to the new
syntax]
it's really weird.
regards,
p
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
