Hide Forgot
it was not 100% reproducible, actually, I couldn't even reproduce it now. from the log and manually run, I found it was caused by "opcontrol --shutdown" stuck when running testing. something blocked oprofile to be shutdown? Need more investigation and it seems like not to be a v7 bug -- at least my knowledge told me -- seems memory/core heavy load caused something unhappily happend?
Any update on this? Is there something that needs to be addressed in the next v7?