When using load balancer with sticky session, what happens to session if associated srever

Typical scenario using load balancer (LB): user logs in, and after successful login, a server behind LB returns a session token. This sess token is proof that user has logged in, and also it is used to correlate session state. Now, only the particular server behind LB, which logged in user, knows the session ID. So user requests need to be directed to same server each time. This is done through session stickiness configured in LB (Other way is to replicate session ID to all other servers, which i am not considering, since in most cloud providers, session stickiness is available, but other way of replicating session ID is not available at all, due to performance etc issues). Q is: what is that particular server holding user session ID, crashes? Is it so that user is simply logged off, loses session state, and starts his session again?