I've failed to reproduce this with Nightly and Debian unstable; I get the warnings about `/sys/devices/system/cpu` but nothing about `/proc/cpuinfo`. It's possible that that line is related to the error (i.e., whatever is trying to open `/proc/cpuinfo` for the second time causes media decoding to fail when it returns an error), but it could also be coincidence.
The browser tab locking up is unexpected, though — even if the media plugin process crashes or hangs, the media subsystem is pretty good about doing everything asynchronously. If try playing something and then kill the `gmplugin` process, it stops playing and I get an in-content error that “something went wrong with playback”, and then it won't play anything until I reload the tab; that's all more or less what I'd expect. If I `SIGSTOP` the process, a few seconds later the audio stops but the time in the UI keeps advancing (and if I `SIGCONT` it, it will resume playing where it left off, which is no longer where the UI says it's playing from; that's an interesting bug but it might be Spotify's and not ours). But, no sign of the content process locking up or crashing.
I've failed to reproduce this with Nightly and Debian unstable; I get the warnings about `/sys/devices/ system/ cpu` but nothing about `/proc/cpuinfo`. It's possible that that line is related to the error (i.e., whatever is trying to open `/proc/cpuinfo` for the second time causes media decoding to fail when it returns an error), but it could also be coincidence.
The browser tab locking up is unexpected, though — even if the media plugin process crashes or hangs, the media subsystem is pretty good about doing everything asynchronously. If try playing something and then kill the `gmplugin` process, it stops playing and I get an in-content error that “something went wrong with playback”, and then it won't play anything until I reload the tab; that's all more or less what I'd expect. If I `SIGSTOP` the process, a few seconds later the audio stops but the time in the UI keeps advancing (and if I `SIGCONT` it, it will resume playing where it left off, which is no longer where the UI says it's playing from; that's an interesting bug but it might be Spotify's and not ours). But, no sign of the content process locking up or crashing.