Data and AI struggles

1,730 problems · 342 companies

DevOps and infra

Jobs and services run out of memory

14 posts from 14 people12d activeSteady, +1 this week

Posts per day

Posts per day14 posts, Aug 28 to Nov 9

The posts behind it

GitHub issuesanthropics/claude-code · ashevchukNov 4

claude-in-chrome: extension shows connected with no console errors, but native host never gets an established connection

## Environment - Claude Code: 2.1.316 (Linux, Arch, kernel 7.2.9-arch1-1) - Chrome: 156.0.8078.79 (stable), single profile (Default) - Claude in Chrome extension: 1.0.105_0 ## Symptom Every claude-in-chrome tool call (`tabs_context_mcp`, `list_connected_browsers`,...

1 reactions1 replies
GitHub issuesBerriAI/litellm · ferr079Oct 25

[Bug]: Proxy startup loops forever and gets OOM-killed during the DST fall-back hour (scheduled_job_stagger)

### Description On the night the clocks went back in Europe/Paris (2026-10-25), the proxy got OOM-killed at exactly 02:00 CET, which is the moment the fall-back hour starts. Every restart after that grew without bound before reaching `Application startup complete` and got killed...

3 replies
GitHub issuespytorch/pytorch · pavan51Oct 25

[Feature Request] Native 1D sliding window extrema (min/max) for torch.signal / torch.nn.functional

...$O(K \cdot N)$ comparisons. For large window sizes ($K \ge 500$), this becomes a major bottleneck. 2. **`tensor.unfold(dim, size, step).max(dim=-1)`**: - Materializes overlapping windows of shape `(..., L_out, K)`, incurring $O(K \cdot N)$ memory overhead. For sequences of...

GitHub issuesoracle/graal · MarcusSammonOct 23

Automated Memory Leak Detection and Destructor Placement

I know that graalvm uses a garbage collector for memory management but I have an idea that may be able to remove the need for garbage collection completely. A memory leak detector for compiled languages could be created using the following algorithm. 1)Compile the program with...

Community forumsCursor Forum · Ale_OrtegaOct 22

Grok Bot Computer Frozen

Where does the bug appear (feature/product)? Grok Bot Describe the Bug I am having some issues with my grok bot and it seems to be stalled. The computer ran out of memory but when I tried to hard reset the bot in Comput…

GitHub issueskubernetes/kubernetes · dimsOct 20

ci-kubernetes-e2e-ec2-scale-correctness-2000 has never passed: Classic ELB 1,000-instance cap and Topology Hints assertion at 2000 nodes

### Which jobs are failing? - `ci-kubernetes-e2e-ec2-scale-correctness-2000`, TestGrid tab `amazon-ec2-release#ec2-master-scale-correctness-2000` - Prow history: https://prow.k8s.io/job-history/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ec2-scale-correctness-2000 The job was...

2 replies
GitHub issuesmagnitudedev/magnitude · bednarix74Oct 18

vulkan: first-load kernel tuning on Intel Lunar Lake (LNL) grows to ~13 GB anon RSS and is OOM-killed; load never completes

## Summary First-time model load on an Intel Lunar Lake iGPU (Vulkan/Mesa ANV) never completes: the one-time kernel-tuning ("Preparing"/"Optimizing") phase grows the `magnitude-inference` worker to ~13 GB anonymous RSS within 5-10 minutes and is killed by the kernel OOM killer /...

1 replies
GitHub issuesBerriAI/litellm · sailtonightOct 14

[Bug]: It frequently runs out of memory—how could I possibly charge for this?

### Description 1 ### Config ### LiteLLM Version 1 ### Steps to Repro 1 ### Which part of LiteLLM is this about? None ### How are you deploying? None

GitHub issuesClickHouse/ClickHouse · ayakovlev-clickhouseOct 12

Concurrency-aware max_threads when it is auto: narrow the query plan when many queries compete for CPU

...at plan time, but only on memory pressure. Under the workload above, memory is not the bottleneck. - `merge_tree_min_bytes_per_read_stream` (26.8) caps `MergeTree` read streams by data volume, but never below `max(16, requested / 4)` streams, and does not consider load. ###...

4 replies
Redditr/GithubCopilot · u/IajahOct 12

Insider unreliable for the past few weeks

...making it harder to understand what your agent is currently doing.. It's been so unreliable that I had to switch back to the stable release to get things done.. I've mostly been using it with Qwen 3.8 27b on a local instance of llama.cpp.. Do you guys have some visibility on...

Stack OverflowStack Overflow [pandas] · Sabri AlyafeiOct 1

Why does my pandas groupby suddenly use 12GB RAM and crash after 1M rows? It worked fine with 100k

I'm working on a FDA dataset exported from BigQuery.. My DataFrame shape is (1124883, 8) - so 1.1M rows and 8 columns.. Before groupby, I checked memory:. df.info(memory_usage='deep') memory usage: 512.4 MB. Columns are: report_number, products_industry_name, outcomes,...

1 replies
GitHub issuesn8n-io/n8n · fluty84Sep 7

Multi-main: workflows lose their schedule and poll triggers when leadership is taken over mid-activation

...re-saving each affected workflow was the only way to recover it. Two things make this hard to notice: 1. There is no operator-visible signal. The workflow is active everywhere you would look, and the activation-errors endpoint is empty. 2. The one log line that records it is at...

2 replies
GitHub issuespola-rs/polars · taozuoqiaoAug 31

Live DataFrames can change silently after `collect()` under memory pressure

## Summary Under sustained direct reclaim in a memory cgroup, a DataFrame matched its reference immediately after `scan_parquet().collect()`, then the same still-live DataFrame changed seconds later. No exception or warning was raised. Changes include all-zero 4 KiB regions and...

1 reactions11 replies
GitHub issuesvercel/next.js · Paliy0Aug 28

Turbopack dev: PostCSS worker runs with the wrong cwd when an ancestor package.json exists, then spawns workers past the pool bound until OOM

...bound. ### Expected The PostCSS worker resolves from the project directory, and a failing worker does not cause unbounded process growth. ### Isolating variables Same machine, same project, same page (byte-identical output): | | processes | memory | result | |---|---|---|---| |...

1 replies

Companies and products named

2 posts
2 posts
2 posts
1 post
1 post
1 post
About this problem

Evidence

14 posts from 14 people in 13 places, about 1 a week over 69 days. Mostly on BerriAI/litellm, pola-rs/polars, vercel/next.js. Tools named alongside: GitHub, Kubernetes, Kernel, Jupyter.

Frustration Frustration 1 of 3· Seen on GitHub issues, Stack Overflow, Reddit, Community forums

How it was grouped

Posts that state a pain and match the "oom" rule. First post Aug 28, 2026, latest Nov 4, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

The same problem elsewhere

Gemini runs out of memory

13 posts from 12 people on GitHub issues.

GitHub runs out of memory

6 posts from 6 people on GitHub issues.

NVIDIA runs out of memory

5 posts from 5 people on GitHub issues.

DuckDB runs out of memory

4 posts from 4 people on GitHub issues.

Apache Iceberg runs out of memory

4 posts from 3 people on GitHub issues.

vLLM runs out of memory

3 posts from 3 people on GitHub issues.

Claude Code runs out of memory

3 posts from 3 people on GitHub issues.

Polars runs out of memory

3 posts from 3 people on GitHub issues.

llama.cpp runs out of memory

3 posts from 3 people on GitHub issues.

Ollama runs out of memory

3 posts from 3 people on GitHub issues.

BigQuery runs out of memory

2 posts from 2 people on GitHub issues. Unverified.

Apache Airflow runs out of memory

2 posts from 2 people on GitHub issues. Unverified.

History

Momentum went from fading to steady.

Nov 9, 2026

Momentum went from steady to fading.

Oct 29, 2026

Momentum went from fading to steady.

Oct 28, 2026

Momentum went from steady to fading.

Oct 27, 2026

Momentum went from fading to steady.

Oct 26, 2026

Momentum went from steady to fading.

Oct 25, 2026

Momentum went from fading to steady.

Oct 24, 2026

Momentum went from steady to fading.

Oct 15, 2026

Momentum went from rising to steady.

Oct 14, 2026

Momentum went from fading to rising.

Oct 12, 2026

Momentum went from steady to fading.

Oct 10, 2026

Momentum went from rising to steady.

Oct 8, 2026