Skip to content
This repository was archived by the owner on Nov 17, 2023. It is now read-only.
This repository was archived by the owner on Nov 17, 2023. It is now read-only.

'Segmentation fault' when using simple_bind operation #865

@lyttonhao

Description

@lyttonhao

Hi, I've got a 'Segmentation fault' when I use simple_bind operation. At first, it occurs when I test my own created layers. Then I find that it occurs in others codes. I simply use the following code from simple_bind example.

import mxnet as mx
import numpy as np
import logging

logger = logging.getLogger()
logger.setLevel(logging.DEBUG)

# we can use mx.sym in short of mx.symbol
data = mx.sym.Variable("data")
fc1 = mx.sym.FullyConnected(data=data, num_hidden=128, name="fc1")
bn1 = mx.sym.BatchNorm(data=fc1, name="bn1")
act1 = mx.sym.Activation(data=bn1, name="act1", act_type="tanh")
fc2 = mx.sym.FullyConnected(data=act1, name="fc2", num_hidden=10)
softmax = mx.sym.Softmax(data=fc2, name="softmax")
# visualize the network
batch_size = 100
data_shape = (batch_size, 784)


ctx = mx.gpu(1)
executor = softmax.simple_bind(ctx=ctx, data=data_shape, grad_req='write')

Then the program may get 'Segmentation fault' at some tests and may be fine at another try. It's quite strange that the error comes out in random. When I change to use mx.cpu(), the program goes fine. However, in my own network, the error always comes out despite the devices.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions