Open SEOJUNGJIN opened 2 years ago
We faced a similar issue in a stress test. As per our analysis, this happens after java heap error is thrown. Once the heap is completely consumed, the SDK shows this endless loop kind of behaviour. In our case the cause of java heap filling up was the byte[] objects which were being held up by NativeStream class.
The SDK wont let them get GC'ed untill you call below method for all the files for whose labelling is completed.
fileHandler.notifyCommitSuccessful(filePath);
When we stress testing the MIP SDK instance (MIP SDK File Sample Source) created as a singleton in the Java Spring environment, the error occurs.
We used MIP SDK is "mip_sdk_java_ubuntu1804_1.12.61_preview.tar.gz", and when an error occurs during the stress testing, the STDOUT contents are as follows. ( https://www.microsoft.com/en-us/download/details.aspx?id=104267 )
Doing a "MIP File::Delete Label" stress test with that MIP SDK for about 5 minutes may copy the error.
This error slows down the process and eventually crashes the process due to stack overflow.
We have already registered with Microsoft Case ( Case No: 32221263 ) and hope that the issue will be resolved as soon as possible.
Thanks!