Crash inside of driver while using a persistently mapped VBO.

GTX950M on driver 430.26
OpenSUSE Tumbleweed on Linux 5.2.1-1-default
Patch that makes the crash occur:
I’m currently working on using Persistent Mapped Buffers to reduce the rendering overhead, however I’ve begun crashing as soon as I tried using it to render text after the start screen.
While sitting in the start screen the text is rendered fine, even with the patch applied, but right after clicking LMB I get a crash

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5fc6a90 in ?? () from /usr/lib64/
(gdb) bt
#0  0x00007ffff5fc6a90 in ?? () from /usr/lib64/
#1  0x00007ffff609a413 in ?? () from /usr/lib64/
#2  0x00007ffff609fec5 in ?? () from /usr/lib64/
#3  0x00007ffff60aa563 in ?? () from /usr/lib64/
#4  0x00007ffff5c22a0b in ?? () from /usr/lib64/
#5  0x0000000000407297 in TextRenderer::render (this=0x7fffffffd538, projection=..., view=...) at ../src/main.cpp:135
#6  0x0000000000408906 in MainState::run (this=0x7fffffffbeb0, window=...) at ../src/main.cpp:301
#7  0x0000000000405ad0 in main (argc=1, argv=0x7fffffffdbf8) at ../src/main.cpp:505

Alright I realized what my mistake was.
So basically every time I resized the VBO I deleted the buffer and then generated it again, completely forgetting that this causes an entirely new buffer with a new id to be created.

So the driver crash was caused by the driver trying to read from the deleted VBO, as the VAO remained not updated.