Comment 11 for bug 1500531

1) Anyone publishing test results to this please also state on what system condition, including whether 32 or 64 bit!

2) The map case implies the error isn't likely a running short of resources problem. It may be a lacking resources problem though, but circumstance rather indicates it is some program error in the sound service package. Perhaps the people providing this for Linux should be contacted about it?

3) It has been indicated before the problem is confined to Linux and 64 bit OS. Is this true? It might also be related to hardware, so perhaps unfixable from Wideland's side.

4) Perhaps we can look for a work-around when prove can be given that only certain sounds (content, format) is involved.