Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Conversation editor never revokes blob URLs of removed attachments

Cerrado
  • ¿Algo no está bien?
#3,185 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

@ManoharPaturi ya está trabajando en esto.

Desde el 13/10/2026.

  • #3186 de @ManoharPaturi — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Área
frontend

Línea de trabajo

Start with ChatInputArea.changeAttachments, which already revokes dropped blob URLs, and compare it with useConversationDraft.changeAttachments, which the ConversationEditor piece editor calls without revoking anything. The attachment chip URLs are created in PromptEditor with URL.createObjectURL. Done means removing an attachment in the draft editor calls URL.revokeObjectURL right away. Pull request #3186 is already open against this issue, so review or build on that work rather than starting a parallel fix.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Describe the bug

In the conversation editor, removing an attachment from a media piece never revokes the attachment's blob object URL. The blob: URL and its File payload stay alive until the whole draft is discarded or the editor unmounts.

ChatInputArea.changeAttachments handles the same removal correctly by revoking dropped blob URLs, but the draft editor path (ConversationEditor piece editor calling useConversationDraft.changeAttachments) forwards the new attachment list straight through with no revocation. Attaching and removing a large file repeatedly during one editing session pins every dropped File in memory.

Steps/Code to Reproduce
  1. Open a conversation in the editor and pick a media piece.
  2. Attach a file (the attachment chip gets a blob: URL from URL.createObjectURL in PromptEditor).
  3. Remove the attachment with the chip's dismiss button.
  4. URL.revokeObjectURL is never called for that URL until the draft is discarded or the editor unmounts.

Repeat 2-3 in one session and the dropped Files accumulate.

Expected Results

Removing an attachment in the editor revokes its blob object URL immediately, the same way the chat composer does.

Actual Results

The URL stays valid and the File payload stays pinned until the draft is discarded or unmounted.

Screenshots

N/A

Versions

OS: macOS
Browser: Chrome
Python version: 3.14
PyRIT version: installed from main (66c41fa)

Lenguaje dominante
Python
Estrellas
4.6k
Forks
944
Merge medio
2 d 16 h
PR fusionados (30 d)
350

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/PyRIT

Todos los issues de microsoft/PyRIT

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.