I've never said anything like that. SMP and JSP are different beasts with different memory allocation policies. SMP uses (generally) more memory than JSP, but provides enhanced performance and smoother UX instead. What I did say, is that I tuned SMP GC policies for more heavy scripts. So, while it uses more memory with light scripts than it could've (i.e. it would accumulate more memory before purging it), it costumes CPU time drastically less with heavy scripts than it would've otherwise (which results in smoother UX and etc and etc).
I see, that makes sense, thanks for the explanation. I couldn't quite relate it to what I's experiencing because other heavy-looking scripts by professional coders didn't increase memory usage as much and my fear was that I was ignoring some basic good practice in my scripts. Eventually I found at least one professional script with a much bigger impact on memory and that reassured me a bit.
Last post by BingoMan -
foobar2000 v1.4.3 Stopped marking the playback of a song when any change of the album in the album list. - Choose album 1, start playing the file - Choose album 2 - Again we select album 1, the reproduced composition is not marked with a triangle.
It was an issue with digital silence on x87 FPUs (so mostly just 32-bit x86).
Thanks for the info. Does this correlate with the x64 binary that ran on Core 2 Duo E6300 Intel CPU? To be sincer, it's unclear to me how are the compilers utilizing the variety of modern (and not) instruction sets, all I see from my experience is that floating point calculations sometimes are much more harder to keep stable (compared to the integer ones).