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

sage sometimes leaves matlab processes that eat 100% cpu time #3504

Open
sagetrac-cwitty mannequin opened this issue Jun 24, 2008 · 0 comments
Open

sage sometimes leaves matlab processes that eat 100% cpu time #3504

sagetrac-cwitty mannequin opened this issue Jun 24, 2008 · 0 comments

Comments

@sagetrac-cwitty
Copy link
Mannequin

sagetrac-cwitty mannequin commented Jun 24, 2008

I've found a way to somewhat reproducibly leave a matlab process eating 100% cpu time.

I log on to sage.math, start Sage, and run the following commands:

sage: m = matlab(matrix(RR, [[1]]))
sage: m.det()

Then I kill my local ssh client with "kill -9" (to make a non-clean ssh shutdown).

Often (not always, but I think more than half the time) this leaves a matlab process eating 100% of the cpu time.

Component: interfaces: optional

Issue created by migration from https://trac.sagemath.org/ticket/3504

@sagetrac-cwitty sagetrac-cwitty mannequin added this to the sage-5.11 milestone Jun 24, 2008
@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@mkoeppe mkoeppe removed this from the sage-6.4 milestone Dec 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants