I've been in the SW game for 10 years. Somewhere I wound up helping devs navigate their career, and I fell in love with it. By day I consult for SW companies, by night I help devs with their careers.
And you're bringing up exactly one of the core elements to this. Terminating the conversation is worse than saying "I don't know."
As for the expectation that you should know the answer, I'd say that is unrealistic. It is commonplace for interviewers to purposefully ask questions until you hit the boundary of your knowledge. They do this to get an idea of your breadth and depth of knowledge. As candidates though, we don't know that is what is happening and how much breadth or depth is appropriate.
For further actions, you may consider blocking this person and/or reporting abuse
And you're bringing up exactly one of the core elements to this. Terminating the conversation is worse than saying "I don't know."
As for the expectation that you should know the answer, I'd say that is unrealistic. It is commonplace for interviewers to purposefully ask questions until you hit the boundary of your knowledge. They do this to get an idea of your breadth and depth of knowledge. As candidates though, we don't know that is what is happening and how much breadth or depth is appropriate.