Yokohama Patch 7 Hotfix 4

  • Release version: Yokohama
  • Updated October 15, 2025
  • 1 minute to read

    • The Yokohama Patch 7 Hotfix 4 release contains fixes to these problems.

    Build information:
    Build date: 10-09-2025_1925
    Build tag: glide-yokohama-12-18-2024__patch7-hotfix4-10-07-2025
    Important:
    For more information about how to upgrade an instance, see ServiceNow upgrades.

    For more information about the release cycle, see the ServiceNow Release Cycle.

    Note:
    This ServiceNow AI Platform major family release is now available in ServiceNow's Regulated Market environments. For more information about services available in isolated environments, see KB0743854.

    Fixed problem

    Problem Short description Description Steps to reproduce

    Analytics Data API

    PRB1945218

    		 Memory leak of JSON serializer in multivis API Each time a data request is processed, a new serializer is created and not released unless a GC is performed, which causes a memory leak.
    1. Create a dashboard.
    2. Add a tab and add 50 identical single score vis:
      • Source: incident.
      • Condition: sys_id is empty.
    3. Duplicate the tab 9 times so there are 500 visualizations in total.
    4. Disable the property 'com.snc.dashboard.streaming.enabled'.
    5. Stop the instance and start again, but don't access the instance in the browser.
    6. Use VisualVM to capture the heapdump.
    7. Search for 'IntegerDateSerializer' in the object list.
      • Observe that there are 0 results.
    8. Access the dashboard created in step 1.
    9. Go over all 10 tabs.
    10. Use VisualVM to capture the heapdump.
    11. Search for 'IntegerDateSerializer'.
      • Observe that there are ~500 results.
    12. Repeat steps 8 through 11 (get the heapdump and search).

    Observe that there are ~1000 results. Each time a data request is processed, a new serializer is created and not released unless a GC is performed, which causes a memory leak.

    OneExtend

    PRB1944861

    		 Revert NASK licensing charge by token to not include input tokens

    The assist charge logged in sys_gen_ai_usage_log is based on 1 assist per 1000 tokens, where tokens = input tokens + 3 * output tokens.

    Fixes included

    Unless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release. Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in.