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

segmentation fault contraction tensor #28798

Closed
LBrunswic mannequin opened this issue Nov 24, 2019 · 6 comments
Closed

segmentation fault contraction tensor #28798

LBrunswic mannequin opened this issue Nov 24, 2019 · 6 comments

Comments

@LBrunswic
Copy link
Mannequin

LBrunswic mannequin commented Nov 24, 2019

The following code generates a segfault in sage-shell. In the notebook, we get a TypeError and a kernel crash.

Parallelism().set(nproc=2) 
M = FiniteRankFreeModule(SR, 3, name='M')
e  = M.basis('e')
x,y,z,t = var("x,y,z,t")                 
Theta = M.tensor((1,1))
for i in range(3):
    for j in range(3):
        Theta[i,j] = function("Theta_"+str(i)+str(j))(x,y,z,t)
Theta["^i_j"]*Theta["^j_i"]  

Note that the error does not occur if one replaces
Parallelism().set(nproc=2)
by
Parallelism().set(nproc=1)

Furthermore, this error did not occur in sage8.9

CC: @egourgoulhon

Component: linear algebra

Keywords: Tensors, parallelism, segmentation fault

Author: Léo Brunswic

Reviewer: Eric Gourgoulhon

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

@LBrunswic LBrunswic mannequin added this to the sage-9.0 milestone Nov 24, 2019
@LBrunswic
Copy link
Mannequin Author

LBrunswic mannequin commented Nov 24, 2019

comment:1

I Tried to find a simpler version of the bug. It does not occur if one replace symbolic functions by a variable.

@egourgoulhon
Copy link
Member

comment:2

This is a duplicate of #27492.

@egourgoulhon egourgoulhon removed this from the sage-9.0 milestone Nov 24, 2019
@LBrunswic
Copy link
Mannequin Author

LBrunswic mannequin commented Nov 24, 2019

comment:3

I'm sorry!

@egourgoulhon
Copy link
Member

comment:4

Replying to @LBrunswic:

I'm sorry!

No problem.
Before opening a ticket for a bug, you may have a look at the bug section of the metaticket #18528 to check if a ticket has not been already opened.

@egourgoulhon
Copy link
Member

comment:5

I am marking the ticket as "positive review" so that it can be closed with the resolution flag set to duplicate.

@egourgoulhon
Copy link
Member

Reviewer: Eric Gourgoulhon

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

2 participants