x10mp3 plugin has been reported to use up all available memory after about 1 hr. should 'electric fence' it for memory leaks.
electric fence didn't reveal anything. user reported the problem was with a firecracker device and bottlerocket on the same port as the x10mp3 receiver.
x10mp3 is read-only, and firecracker is write-only. both should be able to exists simultaneously on the same port. maybe the bottlerocket command sends x10mp3 into wild seizures or something...
so, what needs to happen is install firecracker and run x10mp3 in debug mode to see how x10mp3 handles bottlerocket input.
I have been using firecracker/bottlerocket on the same port as x10mp3 with no problems. Need more info on this one to reproduce. - Cigy
Logged In: YES
Firecracker + x10mp3 on the same port works for me too.
Can't reproduce the problem.