Skip to content
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.

Process keeps running when closed (Windows 11, v. 1.1.4) #342

Open
scippie75 opened this issue Apr 30, 2023 · 5 comments
Open

Process keeps running when closed (Windows 11, v. 1.1.4) #342

scippie75 opened this issue Apr 30, 2023 · 5 comments

Comments

@scippie75
Copy link

When I close the application (v. 1.1.4) on Windows, the process keeps running.
I notice this because my laptop fans keep running at a higher speed as long as the process exists. Once I force kill it, the fans go to normal again.
I've had this multiple times and I think it may always be the case.

@brrd brrd added the need info label May 3, 2023
@brrd
Copy link
Owner

brrd commented May 3, 2023

I can't reproduce this issue. What is your Windows version?

@scippie75
Copy link
Author

scippie75 commented May 4, 2023

That's strange, I'm now watching it and now I haven't had it. But I am very very sure I've had it multiple times before.
I haven't used Abricotine 'for real' on Windows for several days now (usually on Linux), but I'll be using it on Windows again and I'll try to find out what causes it.
It's Windows 11. Great editor by the way!

@scippie75 scippie75 changed the title Process keeps running when closed (Windows, v. 1.1.4) Process keeps running when closed (Windows 11, v. 1.1.4) May 4, 2023
@scippie75
Copy link
Author

I just had it again: I had been editing two markdown documents with two instances of Abricotine. After a while I closed one of them. The fan was going wild for a while and at some point I noticed it and went and check for the processes. I closed the other Abricotine session so that no Abricotine process should run anymore and there it was, using up cpu varying from 0%-12%.

I think I have only had the issues after doing some work on two documents in parallel during several hours with locking and unlocking my Windows in between.

abricotine

@scippie75
Copy link
Author

scippie75 commented May 16, 2023

Update: I have looked at the process in more detail: it seems it is using up all virtual memory space (are you constantly allocating/freeing memory growing in size so that after several hours it comes to a limit?) and uses a gigantic number of cycles.

The process itself seems to have run for 1.5 hour. I don't remember exactly: I have been using it from this morning but I may have closed it in between, although I don't think I did.

abricotine2

@scippie75
Copy link
Author

scippie75 commented May 16, 2023

It may or may not be related, but it was a bit strange, at some point I had a notification on both files that they had been externally changed (which I am certain wasn't the case but one document is stored on Dropbox, the other on OneDrive, so who knows what happened there).

At home,, I regularly work on a document on different computers (shared through Dropbox) and leave them open. So it happens a lot there too.

Maybe it's related?

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

No branches or pull requests

2 participants