Closed ahirner closed 5 years ago
Update: Once I rebuilt the image without CAFFE_OPS it worked. I'll continue with Caffe2 since we need that anyhow.
Hi @ahirner,
Both of the issues disappeared when you built with CAFFE_OPS=OFF?
The second issue seems like it might be related to a wrong GRPC or Protobuf version. Can you show the output of pip3 show protobuf
and pip3 show grpcio
?
Hi @apoms, thx for the response.
The trace dumps right after a docker stop scanner
. SIGKILL isn't picked up after the first error which is why I think the trace is related to db = Database()
. Sry, I should have made that clear.
I was using the latest image on dockerhub, so:
$ docker run --name scanner -it scannerresearch/scanner:cpu pip3 show protobuf grpcio
---
Metadata-Version: 2.0
Name: protobuf
Version: 3.5.1
Summary: Protocol Buffers
Home-page: https://developers.google.com/protocol-buffers/
Author: protobuf@googlegroups.com
Author-email: protobuf@googlegroups.com
Installer: pip
License: 3-Clause BSD License
Location: /root/.local/lib/python3.5/site-packages
Requires: setuptools, six
Classifiers:
Programming Language :: Python
Programming Language :: Python :: 2
Programming Language :: Python :: 2.7
Programming Language :: Python :: 3
Programming Language :: Python :: 3.3
Programming Language :: Python :: 3.4
---
Metadata-Version: 2.0
Name: grpcio
Version: 1.12.0
Summary: HTTP/2-based RPC framework
Home-page: https://grpc.io
Author: The gRPC Authors
Author-email: grpc-io@googlegroups.com
Installer: pip
License: Apache License 2.0
Location: /root/.local/lib/python3.5/site-packages
Requires: six
Classifiers:
Development Status :: 5 - Production/Stable
Programming Language :: Python
Programming Language :: Python :: 2
Programming Language :: Python :: 2.7
Programming Language :: Python :: 3
Programming Language :: Python :: 3.4
Programming Language :: Python :: 3.5
Programming Language :: Python :: 3.6
License :: OSI Approved :: Apache Software License
You are using pip version 8.1.1, however version 10.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
I just ran the same sequences of commands that you did using the latest docker image, but can't seem to reproduce the first error. Are you sure you pulled the latest image?
scannerresearch/scanner cpu 7b465c166f58 47 hours ago 4.55GB
It's definitely weird. Right now, I tried to reproduce it on my macbook with the same docker version as on our workstation. The error doesn't come up. My last guess is it must be the workstation (AMD Ryzen). Edge case!
Closing for now until we can reproduce.
Throws
terminate called after throwing an instance of 'Xbyak::Error'
on latestscannerresearch/scanner:cpu
image and a docker 18.03.1-ce host on Ubuntu 16.04.The local database seems to get initialized.
Similar issues crop up on tensorflow. More specifically, it seems some grpc call goes wrong. This is the stacktrace:
Where does the JIT assembler come in and what else could cause such error?