matlab warning

[sebastian-0x0000ff]

make all ok
make test ok
make matcaffe ok
make mattest 7 passed
but when I ran "net = caffe.Net(model, weights, 'test');" in matlab,I got this
Warning: The following error was caught while executing 'caffe.Net' class destructor:
Error using caffe_
Usage: caffe_('delete_solver', hNet)

Error in caffe.Net/delete (line 72)
caffe_('delete_net', self.hNet_self);

Error in caffe.Net (line 31)
self = caffe.get_net(varargin{:});

In caffe.Net (line 31)

system configuration
Operating system:Ubuntu16.10
Compiler:gcc 5.4
CUDA version (if applicable):8.0
CUDNN version (if applicable):5.1
BLAS:openblas
Python or MATLAB version (for pycaffe and matcaffe respectively):matlab2016b

[sebastian-0x0000ff]

is that ok for ignoring?

[yang-fei]

I have the same problem, have you solved it?
my system:
ubuntu 14.04
gcc 4.8.4
CUDA: 8.0
CUDNN 5.1
BLAS: openblas
matlab2016b

[alireza1370]

I have the same problem!!! have you solved it?
my system:
ubuntu 14.04
gcc 4.9
matlab2016b

[ShaggO]

The problem seems to be caused by the way object initialization is handled in Matlab.
Upon creation of a Net object, the output object (self) is actually created before any code is executed.
The code in Net.m, line 31:

self = caffe.get_net(varargin{:});

replaces the output object and therefore implicitly destroys the original object causing the destructor to be called on an object with an empty hNet_self "pointer".
This is fixable by adding a clause in the destructor checking if self.hNet_sel is empty or not.
I've create the PR #5588 fixing this issue

[alireza1370]

hi, thank you very much, I installed MATLAB2016a and it worked correctly.

…

On 5/4/17, Malte Stær Nissen ***@***.***> wrote: The problem seems to be caused by the way object initialization is handled in Matlab. Upon creation of a Net object, the output object (self) is actually created before any code is executed. The code in Net.m, line 31: > self = caffe.get_net(varargin{:}); replaces the output object and therefore implicitly destroys the original object causing the destructor to be called on an object with an empty hNet_self "pointer". This is fixable by adding a clause in the destructor checking if self.hNet_sel is empty or not. I've create the PR #5588 fixing this issue -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #5346 (comment)