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.

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

Segmentation fault when changing interface mode #895

Closed
rockstorm101 opened this issue Mar 2, 2018 · 8 comments
Closed

Segmentation fault when changing interface mode #895

rockstorm101 opened this issue Mar 2, 2018 · 8 comments
Labels
2.x Non-breaking features and fixes suitable for inclusion in future Printrun 2.x minor releases Reproduced

Comments

@rockstorm101
Copy link
Collaborator

  • OS: Debian 10 Buster
  • Version: 2.0.0rc2

I get a "Segmentation fault" when changing the interface mode. Switching from 'Standard' to 'Compact' interface modes produces:

Failed to run callback after setting "uimode":
Traceback (most recent call last):
  File "/home/rock/Downloads/Printrun/printrun/settings.py", line 352, in _set
    if cb is not None: cb(key, value)
  File "/home/rock/Downloads/Printrun/printrun/pronterface.py", line 282, in reload_ui
    self.splitterwindow.SetSashPosition(self.settings.last_sash_position)
RuntimeError: wrapped C/C++ object of type SplitterWindow has been deleted

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/wx/core.py", line 3190, in <lambda>
    lambda event: event.callable(*event.args, **event.kw) )
RuntimeError: wrapped C/C++ object of type GcodeViewPanel has been deleted
@hroncok
Copy link
Collaborator

hroncok commented Mar 3, 2018

Reproduced.

@hroncok
Copy link
Collaborator

hroncok commented Mar 3, 2018

Switching back to Standard does it as well.

@kliment kliment added Reproduced 2.x Non-breaking features and fixes suitable for inclusion in future Printrun 2.x minor releases labels Mar 3, 2018
@hroncok
Copy link
Collaborator

hroncok commented Mar 5, 2018

When unchecking display temperature graph and clicking OK, I also get Segmentation fault.

@hroncok
Copy link
Collaborator

hroncok commented Mar 5, 2018

Reproduced on macOS.

@kliment
Copy link
Owner

kliment commented Mar 19, 2018

Okay, disabling monitoring seems to make all segfaults go away. So clearly the monitoring timer is sending events to nonexistent objects for some reason

@kliment
Copy link
Owner

kliment commented Mar 19, 2018

I think i got this with 61581e1 - can anyone test?

@hroncok
Copy link
Collaborator

hroncok commented Mar 19, 2018

Confirmed fixed on Linux.

@hroncok
Copy link
Collaborator

hroncok commented Mar 19, 2018

No segfault on macOS either.

@hroncok hroncok closed this as completed Mar 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.x Non-breaking features and fixes suitable for inclusion in future Printrun 2.x minor releases Reproduced
Projects
None yet
Development

No branches or pull requests

3 participants