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

wxMaxima does not close Maxima on closing #1199

Closed
ReneSci opened this issue Jan 15, 2020 · 1 comment
Closed

wxMaxima does not close Maxima on closing #1199

ReneSci opened this issue Jan 15, 2020 · 1 comment

Comments

@ReneSci
Copy link

ReneSci commented Jan 15, 2020

When starting wxMaxima by opening (double-click) a .wxmx file these processes has been initiated:
image
After having executed a Maxima function, this is what i running on the PC:
image
However after closing wxMaxima it still leaves this running and thus preventing a new session:
image
Afterwards, when re-opening wxMaxima, it refuses to execute any Maxima commands until I manually kills the sbcl.exe previously left behind.


If I on the other hand just start wxMaxima (with a empty worksheet) this is seen:
image
Running some Maxima functions does not start any extra sbcl.exe and the whole wxMaxima/Maxima complex shuts down as expected.

Also, if I start wxMaxima and opens a file form within wxMaxima, it also works fine.

Drag and drop also works fine.


So it seems like the double-click (opening a file on he command line) initiates an extra sbcl.exe where one of them is not being used.

wxMaxima version: 20.01.2-DevelopmentSnapshot
using wxWidgets version: wxWidgets 3.1.3
Maxima version: branch_5_43_base_264_g292ed6cfd
Maxima build date: 2020-01-15 00:05:44
Host type: x86_64-w64-mingw32
System type: Win32 10.0.17134 X86-64
Lisp implementation type: SBCL
Lisp implementation version: 1.4.14
wxMaxima's idea of the directory layout is:
User configuration dir: C:\Users\xxxxxx/maxima/
Help dir: C:\maxima-current\share/doc/wxmaxima

@ReneSci
Copy link
Author

ReneSci commented Jan 16, 2020

No - it still leaves a sbcl.exe behind when closed:
image
One for each time wxMaxima is opened:
image

However, now the next session works normally, so the user will not see the sbcl.exe left behind.
And - still this only happens when the windows double-click is used to open a wxmx file.

gunterkoenigsmann added a commit that referenced this issue Jan 16, 2020
daute added a commit that referenced this issue Oct 13, 2024
Until now, the pid was not set (and -1
was printed during the logging). This
(hopefully) helps with issues, where
the "not killing" of Maxima processes
was reported, e.g. #1199, #1824, #1922
or #1963.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant