Back to Feed
Benchmarks & Evals / Multimodal

Benchmarking Visual Evidence in Issue Localization

Original: MM-IssueLoc: A Controlled Benchmark for Evaluating Visual Evidence in Multimodal Repository-Level Issue Localization

Listen to the summary

Uses a voice available on your device

Audio options
On this page 4 sections
Related concepts 4 concepts

Key Takeaways

  • The MM-IssueLoc benchmark includes 652 issue-PR instances across 23 languages with both file-level and function-level gold labels.
  • A non-trainable Visual Content Evidence adapter simplifies OCR and UI elements into structured text blocks for improved agent input.
  • Removing visual input causes a performance drop of 4.44 in the File@5 score for the MM-IssueLoc-VL-Embedding-8B retriever.
  • The OpenHands agent with GPT-5.2 achieves a File@5 score of 38.96 on the benchmark.

Summary & Methodology Analysis

The researchers constructed the MM-IssueLoc benchmark to address a gap in existing tools that struggle to isolate the role of visual evidence in software maintenance. They created a diagnostic instrument by annotating 1,050 issue images with seven evidence categories and four relevance levels. This allows developers to assess if images provide helpful information or distract localization agents. The architecture supports four input modes: text-only, with-image, Visual Content Evidence (VCE), and VCE+image. The VCE adapter is a non-trainable component that converts OCR output, error signals, and UI elements into structured textual blocks, providing the agent with meaningful visual context without requiring additional fine-tuning, which is the process of adjusting a pre-trained model on a specific dataset.

Interactive System Flowchart

Click diagram to expand and zoom

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is the primary purpose of MM-IssueLoc?

It serves as a controlled benchmark to determine whether visual evidence helps, hinders, or is ignored by AI agents when localizing software issues.

Q2. Does this benchmark focus only on English-based code?

No, it covers 652 issue-PR instances across 23 languages.

Q3. Is this a tool for generating patches?

No, it is a benchmark designed for evaluating localization, not end-to-end patch generation.

Q4. What is a retriever in this context?

A retriever is a model used to search for relevant files or functions in a codebase, here represented by the MM-IssueLoc-VL-Embedding model, which uses a curriculum learning approach with hard negatives to improve search accuracy.

Q5. How does the VCE adapter function?

The VCE adapter extracts OCR results, error signals, and UI elements into structured textual blocks that the localization agent can process.

Q6. What happens when visual data is removed?

For the MM-IssueLoc-VL-Embedding-8B model, removing images results in a 4.44 decrease in the File@5 score.

Q7. What is the best-performing file-level agent mentioned?

OpenHands using GPT-5.2 achieves a File@5 score of 38.96.

Q8. What are the limitations regarding image handling?

The current retriever is limited to a maximum of two images per issue, and the harmful-image subset used for stress testing is not representative of real-world frequency.

Q9. Does the VCE adapter represent the upper bound of visual reasoning?

No, the VCE uses a fixed set of extraction fields and does not represent an upper bound on visual reasoning performance.