@nrobh
You doubt someone took 5 minutes to load? I already took more then 5 minutes to load, so it's totally possible. This scenario is exactly what I've been telling here, this guy was suspended in loading screen, which triggered the message and wouldn't allow you to start. As soon as his loading was resolved (either by finishing or quitting), things went back to normal.
If you believe it might have something to do with the game not recognizing he isn't loading, this doesn't necessarily counts as a bug, but rather probably a programming oversight. His client didn't tell the server he isn't loading anymore, so the server still thinks he is loading. As I've been waiting for a loading that went over 5 minutes, I believe there's no timeout feature for this, which means if the client stays hung up for say 8 minutes, the game will wait these 8 minutes until the client forwards the message it isn't in this lobby anymore. I'd go further and say that if a client gets eternally stuck in loading screen and doesn't do anything about it, the lobby will stay this way forever.
And also, it's fairly normal that after a crash on the client it takes a fair amount of time for the server to realize that client has left the lobby.
I'm sure if DICE changed the message to "Waiting for X Players to load" when the room is full but not everyone has loaded yet, this doubt would vanish.
@LOTR2013
Has any of us been on that situation? Yes, I've been the guy who took ages to load, and also the guy who got a friend on this situation while talking via discord, so it was clear this was the case. When I was loading, they would see "Waiting for 1 Player" and as soon as I loaded the message vanished, and counter started. Similarly, when my friend was taking ages to load, I was seeing the message, and as soon as he confirmed to me he loaded, the message vanished and countdown started. So here's my proof.
It happens too often, true, but crashes happen very oftenly in life, you're very lucky to still believe crashes aren't something that happen all the time. My PC crashes almost everyday I use it, be itself, or just an app I use on it.
For your situation where "the bug fixed itself" it's nothing more then the lazy loader finally loading the game without a crash. As I said before, I already took more then 5 minutes to load.
And about calling it a BUG, I understand it can be called that, but then people instead of understanding what it really means, they'll just stay away from it as if it was something which can't be dealt with. However, I never left any match that this happened after I realised it was a loading issue, and I always played the match afterwards, it always fixed itself. So to me it's better not to call this a BUG, but simply a design flaw.
To finish this, a few examples of why my PC crashes: It gets very hot; I suspend it without a restart for a long time; I have more applications open eating my RAM; Windows decides to download the Windows Updates; Origin crashes; Nvidia crashes; Nvidia decides it's time to update; My power cable unplugs and when I realise it, it already sent me back to desktop and the game probably crashed with that.
In a console, many of these situations can also happen. Another good reason for crashes is the machine getting old, and I believe many players have computers/consoles from 2 or more years ago.