Fix NaN/Inf values in dV gradients during backward pass #122
+309 −13
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
This PR fixes a critical numerical stability issue where NaN/Inf values would appear specifically in
dVgradients during the backward pass of the Triton implementation, whiledQ,dK, forward output, and softmax log-sum-exp remained numerically stable.Problem
The issue manifested in the following configuration:
Root Cause
The issue was caused by three factors:
dvanddktensors were initialized usingtorch.empty_like()which could contain garbage values including NaN/Infdo(gradient of output) loading could introduce uninitialized valuesSolution
This PR implements a comprehensive fix with multiple layers of protection:
1. Proper Tensor Initialization
2. Gradient Accumulation Safety Checks
3. Input Validation
4. Store Function Safety Guards
Testing
Added comprehensive test suite (
test_dv_nan_fix.py) that validates:Impact
Fixes #121.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.