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

When use Eraser tool, docker server sometimes shows error #608

Open
seon-creator opened this issue Jul 5, 2023 · 4 comments
Open

When use Eraser tool, docker server sometimes shows error #608

seon-creator opened this issue Jul 5, 2023 · 4 comments

Comments

@seon-creator
Copy link

When I use Eraser tool after using Magic wand to make segmentation data, sometimes mouse curser moves slowly and stop.
After then, window changed with error message.
How to solve the problem?

coco_error

@SixK
Copy link

SixK commented Jul 5, 2023

Maybe you need more Ram ?
I also noticed this problem on my computer (16Gb Ram) with large datasets and large class list (about 80 classes) after few images annotations.
I usually restart my docker containers to get speed back and be safe for more images annotation.
When it slow down, delete less pixels at once to avoid crash.

I don't have investigated this problem.
I dunno if we have this situation because we had javascript errors and memory is not released (there is few bugs actually leading to javascript errors in some cases) or if there is another problem eating memory.

I didn't tried using my Vue3 coco-annotator version on large dataset to see if there is still the problem.

@seon-creator
Copy link
Author

I saw the CPU Mem usage of the coco-annotator.
When erase anotated area, if too much segmentation, It works slowly.
I agree your opinion. Thank you ^^

@SixK
Copy link

SixK commented Jul 7, 2023

Seem's I also have weird behaviours on low memory conditions when using my coco-annotator Vue3 port.
I don't know if this could have something to do with default docker heap memory size.
I find no related post with vue.js on this.
I'll have to try adding "shm_size: 512mb" to my docker-compose file.

I will also have to search for potentials memory leaks.

@SixK
Copy link

SixK commented Jul 7, 2023

Forget my assumption about shm_size.
I had few bugs I fixed now and anyway problem happens in web browser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants