[bug] `log_history_model` causes the app to crash

### Describe the bug
The app sometimes just crashes when the mouse is hovering at the log viewer widget when the app is started. The mouse position may have nothing to do with the actual crash. One of the causes is the `internal pointer` of the data is pointing to an invalid address when it's being interpreted as a string

### To Reproduce
Start the application while having the mouse pointer at the place where the log viewer widget should be spawned.

### Expected behavior
There is no crash.

### Desktop (please complete the following information):
- OS Windows 11
- OS version 10.0.22000
- Commit hash 0e6fbf3dfe92269f9d21456ef680b8f9923ec420

Start by reproducing the crash on Windows 11 with the mouse over the log viewer widget during application startup. Then inspect log_history_model where the data's internal pointer is interpreted as a string; done means the application no longer crashes in this scenario.

Written by the indexing model from the issue text.