Skip to content

Studio bypasses HyperFrames existing cross-project render lock. #7457

Closed

Description

@yaronelh

Describe the bug

The CLI normally allows only one local render per user account; others wait. But Studio calls the renderer directly without acquiring that shared lock. each render sizes its workers against the whole machine, independently of other renders.

Minimal reproduction

export async function acquireRenderSlot(
plan: Pick<RenderPlan, "project" | "waitForRenderSlot">,
signal?: AbortSignal,
lock: Partial<RenderLockOptions> = {},
): Promise<() => void> {
try {
return await acquireRenderLock({
project: plan.project.dir,
wait: plan.waitForRenderSlot,

state.progress = j.progress;
if (j.currentStage) state.stage = j.currentStage;
};
await executeRenderJob(
job,
opts.project.dir,
opts.outputPath,
onProgress,

Steps to reproduce

Clicking the render button

Expected behavior

Other renders are locked

Actual behavior

All renders are open

Environment

I don't know if I can run this. It is hyperframes studio on Windows 11

Additional context

No response

Activity

  1. added
    bugSomething isn't working
    triage/needs-triageNeeds current-behavior, related-work, and scope evaluation.
    on Nov 9, 2026
  2. self-assigned this
    on Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingtriage/needs-triageNeeds current-behavior, related-work, and scope evaluation.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions