aws / aws/amazon-sagemaker-feedback

JupyterLab notebook crashes consitently when using huggingface's transformers

Open
#138 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
10
Forks
3
PR merge metrics
No merged PRs in 30d

Description

### Product Version

- [ ] Amazon SageMaker Studio Classic
- [X] Amazon SageMaker Studio
- [ ] Issue is not related to SageMaker Studio

### Issue Description

Sagemaker notebooks always crash and restart when using transformers processors regarless of memory machine spec.

Tried following machine specs:
- 4, 8 and 16 GB of RAM
- 5, 10, 15 GB of disk space

Python Kernel: Python3 ipykernel

Minimum example I was able to reproduce the issues 100% of the time.

```
from transformers import CLIPProcessor

processor = CLIPProcessor.from_pretrained("openai/clip-vit-base-patch32") # or literally any other string

"DONE"
```

Screenshot 2024-10-08 at 22 23 45

### Expected Behavior

1. Create empty notebook and launch any machine
2. Create following cell
```
from transformers import CLIPProcessor

processor = CLIPProcessor.from_pretrained("openai/clip-vit-base-patch32") # or any literally any other string

print("DONE")
```
3. Run the code

Expected: cell to succeed and "DONE" is printed

### Observed Behavior

1. Create empty notebook and launch any machine
2. Create following cell
```
from transformers import CLIPProcessor

processor = CLIPProcessor.from_pretrained("openai/clip-vit-base-patch32") # or any literally any other string

print("DONE")
```
3. Run the code

Observed: Kerner Restarted

### Product Category

JupyterLab

### Feedback Category

Reliability and Stability

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

The payload names no repository files, tests, or implementation entry points. Start by reproducing the minimal CLIPProcessor notebook in Amazon SageMaker Studio across the listed memory and disk sizes, then inspect the available kernel or JupyterLab diagnostics; done means the kernel remains running and prints "DONE".

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, huggingface, jupyter, python
Domain
cloud, machine-learning
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.