search

Cuperino / QPrompt-Teleprompter

Teleprompter software for all video creators. Built with ease of use, productivity, control accuracy, and smooth performance in mind.
https://qprompt.app
GNU General Public License v3.0
357 stars 23 forks source link

Occasional app crash when invoking the Prompt mode #97

Closed videosmith closed 1 year ago

videosmith commented 1 year ago

Bug Description When switching from Edit to Prompt mode, either by mouse click or hotkey, the program closes. Will provide more info, if I can reproduce the issue on demand.

Steps to Reproduce

  1. Difficult as it only happens occasionally.
  2. Clicking on the Start Prompting button or a keyboard shortcut (through a ShuttleXpress script) crashes the program.
  3. Only other app open is the resident code for the ShuttleXpress driver.

Expected behavior Should go into prompt mode as it usually does

Detailed description of display configuration (if applicable) RPi 400, Raspberry Pi OS, latest updates, Same 1.0.0 release build of QPrompt as in the past. HDMI 0 only in use

Cuperino commented 1 year ago

Is transparency enabled when this happens?

videosmith commented 1 year ago

I wonder if this is related to #115?

Cuperino commented 1 year ago

It could be related. The list of bookmarks gets regenerated in various specific circumstances. Toggling the prompter is one of them.

Cuperino commented 1 year ago

It turns out this bug is unrelated to #115 because #115 wasn't caused by a dangling pointer, but by an out of bounds access attempt that is never executed while invoking prompt mode.

Cuperino commented 1 year ago

Let me know if this bug ever manifests itself again. I think there's a chance I might've squashed it in v1.1.1.

videosmith commented 1 year ago

No. Only opeeating in full screen selecting prevoius marker - even if only one marker placed On Wednesday, July 27, 2022, 03:17:01 PM EDT, Javier O. Cordero Pérez @.***> wrote:

Is transparency enabled when this happens?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

Cuperino commented 1 year ago

Does this crash still occur? I have reason to believe I may have fixed this issue in v1.1.1, but I have no way to be sure because I haven't been able to replicate it.

videosmith commented 1 year ago

So far, no. Still on 1.1.1 though due to animation issues with 1.1.2 on RPi. On Tuesday, October 11, 2022 at 12:27:33 PM EDT, Javier O. Cordero Pérez @.***> wrote:

Does this crash still occur? I have reason to believe I may have fixed this issue in v1.1.1, but I have no way to be sure because I haven't been able to replicate it.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

Cuperino commented 1 year ago

Alright. If the issue doesn't happen again and no one reports an issue that might be related, I may to close this issue as "potentially solved" after v1.2.0 or a later release.

Edit: Changed v1.2.1 to v1.2.0 because the extra v1.1.3 was released when v1.2.0 was initially thought to come out.

Cuperino commented 1 year ago

This issue seems to have been successfully solved long ago, and the startup crash that that was fixed in v1.2.0-03 is not related to this. Closing as solved.