Probably unrelated (except that it probably was an earlier crash that caused the lock file to be left behind without getting deleted). If the old lock file still exists and may have the wrong file permissions, the new one can’t be created. This helped other people but is a bit too heavy-handed:
… as @Nepherte correctly says in the subsequent post:
What should be done is to find the specific Roon lock file in /tmp and delete it specifically, or find the permission problem and correct it, not change ownership on the directory