Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Segmentation fault and crash on save as #43

Open
wltjr opened this issue Sep 10, 2018 · 5 comments
Open

Segmentation fault and crash on save as #43

wltjr opened this issue Sep 10, 2018 · 5 comments
Assignees
Labels

Comments

@wltjr
Copy link
Member

wltjr commented Sep 10, 2018

Description

When saving as a new file or a recent file it crashes with a segfault

Steps to reproduce
  1. Create a new file or open a new one
  2. Modify document
  3. Click save as
  4. Select a recent file or enter a new file name
  5. Click ok/crash
    ...
@wltjr wltjr added the bug label Sep 10, 2018
@wltjr wltjr self-assigned this Sep 10, 2018
@ApostolosB
Copy link

Hmmmm. I don't see this.

@wltjr
Copy link
Member Author

wltjr commented Sep 10, 2018

It is happening for me pretty consistently, 2 ways to reproduce.

Existing document

  1. open existing document
  2. save as another
  3. crash (document ends up empty)

Recent document

  1. open recent file from editor (select file from drop down at top)
  2. crash on edit

I am working on the 2nd one. I wanted to get rid of that drop down select box for the recent files. I was thinking some sort of list next to the other areas. That drop down select box is quirky. Though it may remain if I can fix it as it is now.

@ApostolosB
Copy link

Yep. Reproduced it. Was doing it wrong. Sorry.

@wltjr
Copy link
Member Author

wltjr commented Sep 10, 2018

No worries it has a few particular paths to trigger. I can open a file, even a recent file by selecting it in the file navigator. But not if I select it from the drop down recent files list. The crash only happens when you attempt to modify the recently opened document. So seems opening the file is fine, but something else is going wrong causing the crash. Only when the document is opened via selecting a recent file.

The saving as a file breaks if you open an existing document. You can save a new document just fine.

Other related operations seem fine, its just those two scenarios it seems to consistently crash.

@wltjr wltjr pinned this issue May 22, 2019
@wltjr
Copy link
Member Author

wltjr commented May 22, 2020

Seems to be a deficiency in elm_code per elm code task #T6608

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants