-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Crash on file reading after initial use #22
Comments
Encountered the same bug today: crash (unable to restart OBS unless the plugin is uninstalled). Laptop:
|
After some additional testing: the crash seems to be triggered when reading from a file containing two or more subsequent empty lines. In my case this is consistently reproducible. Expected and preferred behavior for two or three emptly lines: an empty slide. |
Thanks for the testing and the insight. Can you attach a copy of the text file that you have found is able to consistently crash the plugin? |
Here you go: OTSS Normal.txt Tested with identical file names. |
Thanks for providing the files. Looks like the crash is reproducible on my end which is good. I will look into debugging and pushing a fix for it when I get the chance |
That's great to hear. |
Multiline file reading crash has been fixed on linux but still needs to be tested on Windows and Macos. Further examination of the file reading logic can also be done to allow for certain blank lines to be read as a blank slide
Extra new line characters are now appended to the next slide or are treated as blank slides if surrounded by new line characters
Fixes for the mentioned bugs have been tested on Linux and pushed to the dev branch. Need to conduct testing on Windows and MacOs before merging to master and releasing a new version |
Describe the bug
Crash on file reading after initial use
Desktop (please complete the following information):
Additional context
Mirror of reported issue from MMTech1 on the OBS discussion forum here
crash-2021-10-16-11-04-20.txt
The text was updated successfully, but these errors were encountered: