Was this helpful?
Was this helpful?
In this Article
  • Created

Article Map View Freezing with 100+ Active Jobs Plotted

Summary

The Dispatch Map view becomes unresponsive or crashes when displaying more than 100 active jobs simultaneously, particularly affecting operations with large geographic coverage or high job density.

Symptoms

  • Browser tab freezes within 3–5 seconds of loading the Dispatch Map
  • Map tiles render but job markers remain in a loading state indefinitely
  • Chrome displays "This page is unresponsive" warning; Safari shows "This webpage is using significant memory"
  • Issue is more pronounced on lower-spec machines or when multiple browser tabs are open
  • Zooming or panning the map triggers additional freeze events

Affected Versions / Platforms

FieldPulse Web App 3.1.2 – 3.2.0
Chrome 120+, Safari 17+, Edge 120+
Windows 10/11, macOS 13+
Not affected: Mobile app map view (uses native rendering)

Cause

In my experience working with organizations that have scaled to 50+ technicians, this issue stems from how the legacy map rendering engine handles marker clustering. Prior to version 3.2, the platform rendered each job as an individual DOM marker element rather than using canvas-based clustering. At 100+ markers, the browser's memory footprint exceeds 500MB for the map tab alone, triggering garbage collection cycles that manifest as UI freezing.

What I typically recommend understanding is that this is fundamentally a client-side rendering limitation, not a data loading issue. The API returns the job data efficiently; the bottleneck occurs during visualization.

Resolution

Immediate mitigation (no update required):

  1. Apply map filters before viewing — Filter by Technician, Status, or Date Range in the left panel to reduce rendered markers below 75
  2. Use Territory Views — Configure Territory-based dispatch boards to auto-filter jobs by geographic region
  3. Disable live location tracking — Toggle off "Show technician locations" in the map layer menu (reduces marker count by ~30%)

Permanent fix:

Update to FieldPulse 3.2.1 or later, which introduces canvas-based marker clustering with automatic level-of-detail reduction. In my experience deploying this across multiple implementations, the new renderer maintains 60fps with 500+ markers.

  1. Navigate to Settings > System > Updates
  2. Verify current version; if below 3.2.1, select Update Now
  3. Clear browser cache (Ctrl+Shift+R or Cmd+Shift+R) to ensure new map assets load
  4. Test Dispatch Map with your typical job volume

Workaround

For organizations that cannot update immediately, what I typically recommend is a two-board workflow: use the List View for high-volume dispatching and reserve the Map View for route verification with filtered subsets. This has proven effective for teams managing 150+ daily jobs across our client base.

Note: The workaround does have limitations — you lose the visual geographic context during initial assignment, which some dispatchers find disruptive. I acknowledge this is not ideal for operations where proximity-based assignment is critical.

Status

Resolved in 3.2.1 — Canvas-based clustering implemented.

If you continue experiencing freezes after updating, please verify that your browser meets our supported browser requirements and that hardware acceleration is enabled in browser settings.