You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This fix allows the current tab to be the one targeted by typing and commands: limetext/lime-qml@5416f3b
After that commit, it is now possible to crash lime-qml by opening a file, closing an older one and typing in it. It looks like the backend is destroying a buffer it shouldn't when the close command is issued.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36333201-close-file-destroys-wrong-buffer?utm_campaign=plugin&utm_content=tracker%2F15716642&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F15716642&utm_medium=issues&utm_source=github).
The text was updated successfully, but these errors were encountered:
This fix allows the current tab to be the one targeted by typing and commands: limetext/lime-qml@5416f3b
After that commit, it is now possible to crash lime-qml by opening a file, closing an older one and typing in it. It looks like the backend is destroying a buffer it shouldn't when the close command is issued.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: