Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Lua Editor: Using "Next Document Tab" while there is no Lua script open silently crashes the Lua Editor #7344

Open
LB-ArturZieba opened this issue Feb 2, 2022 · 1 comment
Open

Lua Editor: Using "Next Document Tab" while there is no Lua script open silently crashes the Lua Editor #7344

LB-ArturZieba opened this issue Feb 2, 2022 · 1 comment
Labels
feature/scripting This item is related to the scripting tools. good-first-issue Issue ready for a new contributor according to the help wanted guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/major Major priority. Work that should be handled after all blocking and critical work is done. sig/content Categorizes an issue or PR as relevant to SIG Content. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@LB-ArturZieba
Copy link
Contributor

Describe the bug
Using the View > Next Document Tab action in the Lua Editor while there is no Lua script opened causes it to silently crash. This issue does not occur when using the View > Prev Document Tab and it also does not occur while any Lua script is opened. No generated crash.log was found after this issue.

Steps to reproduce
Steps to reproduce the behavior:

  1. Go to Tools > Lua Editor.
  2. With no Lua script opened go to View > Next Document Tab.

Expected behavior
The Lua Editor crashes silently.

Actual behavior
Nothing happens.

Video

LuaEditorNextDocumentTab.mp4

Found in Branch
Development (d6c419d)

Desktop

  • Device: PC
  • OS: Linux
  • Version: Ubuntu 20.04.3 LTS
  • CPU AMD Ryzen 5 3600
  • GPU NVIDIA GeForce RTX 2060 SUPER
  • Memory 16GB
@LB-ArturZieba LB-ArturZieba added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/content Categorizes an issue or PR as relevant to SIG Content. priority/major Major priority. Work that should be handled after all blocking and critical work is done. labels Feb 2, 2022
@monroegm monroegm added triage/accepted Indicates an issue or PR is ready to be actively worked on. feature/scripting This item is related to the scripting tools. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 2, 2022
@guillaume-haerinck guillaume-haerinck added the good-first-issue Issue ready for a new contributor according to the help wanted guidelines. label Dec 6, 2024
@LafLaurine
Copy link
Contributor

Tried on Windows, seems like I can't reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature/scripting This item is related to the scripting tools. good-first-issue Issue ready for a new contributor according to the help wanted guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/major Major priority. Work that should be handled after all blocking and critical work is done. sig/content Categorizes an issue or PR as relevant to SIG Content. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@guillaume-haerinck @LafLaurine @monroegm @LB-ArturZieba