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

Notepad ++ crashes in case of temporary files is opened in notepad++ and system shuts down #2730

Closed
ghost opened this issue Dec 30, 2016 · 8 comments
Labels

Comments

@ghost
Copy link

ghost commented Dec 30, 2016

Description of the Issue

Notepad ++ crashes in case of temporary files is opened in notepad++ and system shuts down.

Steps to Reproduce the Issue

  1. Open few files in Notepad ++.
  2. Open a file from outlook or any file which is temporary file.
  3. try to shut down windows as standard process.
  4. start your system again.
  5. Start notepad++
  6. You will fined there are no tabs open which is available in normal case when you restart your system.

Expected Behavior

Tabs should remain open whenever next time i open notepad++. which is default functionality of it.

Actual Behavior

there are no tabs open which is available in normal case when you restart your system.

Debug Information

@creckord
Copy link

creckord commented Feb 1, 2017

I'm not sure if this is the same, but whenever my Windows forces an unattended restart to apply updates, I lose all unsaved content (tabs for new and temporary files are gone, "regular" files are reopened but unsaved changes are lost).

If on the other hand, I just close Notepad++ (or even kill it hard through Task Manager), all unsaved content is restored from session.

@Gabr-F
Copy link

Gabr-F commented Feb 1, 2017

@kushalagrawal Does it really crash? From the rest of your message it looks like the problem is "just" that the now-missing files are ignored when reloading the session.
Please fix the title and the post if it's so.

@Gabr-F
Copy link

Gabr-F commented Feb 1, 2017

@creckord Does Notepad++ crash whenever that (unattended restarts to apply updates) happens? Does it display the various messages that an exception occurred, that it will attempt to save any unsaved data etc.?

P.S. I'm not sure what you mean with unattended restarts, if you mean you're not in front of the PC I guess you can't verify this...

@GoRadioGo
Copy link

Yes, I saw the same thing today.
My Notepad++\backup directory was missing about 1/2 of my unsaved files.

It appeared to happen same way as @creckord

N++ Auto-backup work(ed) flawless for me for over a year.
Today I stepped away from my computer for a while, and upon my return, saw that Windows 10 had restarted on it's own.
In opening N++, not all 'unsaved' files were restored. Yikes !

@donho donho added the reject label Jun 13, 2017
@donho
Copy link
Member

donho commented Jun 13, 2017

It's not a crash issue.

@donho donho closed this as completed Jun 13, 2017
@GoRadioGo
Copy link

As mentioned, my behavior was same as @creckord Feb 1

I have no evidence it was a crash. But Windows forced an unattended restart.
The main evidence is though that files were lost.

Granted the Subject line of this original issue may have been a misnomer.
But the issue is real. Surprised issue would be closed.

@creckord
Copy link

After just losing files for yet another time upon Windows restart, I dug around a bit, and I think I found out what went wrong for me: Sometimes, I lose my session backup configuration settings.

  • I'm normally using Notepad++ in mono-instance mode and have session snapshot/periodic backup enabled
  • Ever so often, I still need to launch a separate Notepad++ instance. I do this with -multiInst -nosession (I use this as my default editor for command-line Git)
  • That separate Notepad++ instance has session snapshot/periodic backup disabled by default
  • Depending on whether or not I have my regular mono-instance Notepad++ still running at the time and/or the order in which I close the two, this config change sticks and propagates to the mono-instance
  • A subsequent restart (or killing Notepad++ any other way) naturally loses all new stuff...

I'm currently working around this by restoring the setting in config.xml via sed whenever the Git editor exits. Is there a way to separate the configs, e.g. specifying a separate config folder, or to tell Notepad++ that this is a one-off instance and it shouldn't persist config?

@donho
Copy link
Member

donho commented Nov 1, 2022

Fix by 6000f3b

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

Successfully merging a pull request may close this issue.

4 participants