IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing a Panel PC Virtual Memory Warning in Web HMIs

Panel PCs and displays Published 6 min read

Short answer

The warning means the browser is holding the main HMI page and the embedded iframe page at the same time and Windows commit charge has reached its limit. Replace the iframe with a button that navigates to the dashboard page, so only one page stays in RAM. A larger paging file or another browser does not add RAM or lift the operating system's browser-version ceiling.

On this page
  1. What the warning measures
  2. Why the iframe doubles the bill
  3. The fix: navigate instead of embed
  4. Worked example: the arithmetic on a 4 GB panel
  5. Two changes that look like fixes but are not
  6. Separating memory pressure from a tag fault
  7. When the panel has to go
  8. Questions asked

The warning is a capacity message, not a tag fault and not a dying panel: the browser is holding the main HMI page and the embedded dashboard page at the same time, and Windows commit charge has reached its limit, which is physical RAM plus the paging file. The fix that works on the existing panel is to stop embedding: replace the iframe with a button that navigates the browser to the dashboard page, so only one page sits in RAM at a time. On a 4 GB panel with a 0.5 GB paging file, the embedded layout ends a shift at 4.4 GB of a 4.5 GB commit limit, while the navigated layout peaks at 3.3 GB, so the warning disappears with over 1 GB of headroom. A larger paging file only masks the warning, and another browser is not available on a Windows generation this old. If one page at a time still does not fit, the visualization has outgrown the panel and the move is current hardware.

What the warning measures #

Windows raises the low-memory warning when commit charge, the memory the system has promised to every running process, approaches the commit limit: installed RAM plus the paging file. On panel PCs of this generation the paging file usually lives on a small, slow system partition, so the practical ceiling sits close to installed RAM. The browser is the process that reaches it, because a web HMI keeps its scripts, images, rendered page and live-data subscriptions in memory for as long as the page stays open.

Read the Windows performance graphs while the warning is on screen. Commit near the limit with a quiet CPU means capacity. Correct, updating process values next to the warning confirm it; a tag fault gives wrong or missing values, not an OS message. This is also not the panel failing. Hardware death shows up as blank screens or boot faults, which is panel PC dark screen troubleshooting territory.

Why the iframe doubles the bill #

An iframe is not a snapshot of the dashboard. It is a second live document: the parent HMI page keeps its own DOM, scripts and data subscriptions, and the embedded page builds its own on top of that. You pay for both for as long as both are open, and the size of the bill is set by the embedded page's own weight, not by anything you can tune in the HMI project.

That matches how the fault arrived: the plain HMI ran clean, and the warnings started the moment the dashboard page was embedded. Holding two pages on one screen is exactly the trade-off behind embedding third-party pages in an HMI iframe, and on an old panel it is the most expensive line in the browser's memory budget.

The fix: navigate instead of embed #

  1. In the HMI project, find the iframe widget that holds the dashboard page and copy its target address.
  2. Replace the widget with a button whose action navigates the current browser window to that address, the same window and not a new tab, because a new tab keeps both pages alive.
  3. Put a return button on the dashboard page that navigates back to the main HMI page, so the operator has a one-press path back.
  4. Deploy, then repeat the exact operator sequence that fired the warning while watching commit against the limit.

Peak memory becomes the larger of the two pages instead of their sum, because the browser unloads the HMI page when it navigates away. Test the change with the machine in a safe state: during the page swap the operator briefly has no HMI view.

Worked example: the arithmetic on a 4 GB panel #

Illustrative numbers, so read your own from the performance graphs:

Item Value
Installed RAM 4.0 GB
Paging file 0.5 GB
Commit limit (4.0 + 0.5) 4.5 GB
Windows and background services 2.4 GB
Browser holding the main HMI page 0.9 GB
Embedded dashboard page at load 0.7 GB
Dashboard growth over one shift 0.4 GB

Main page alone: 2.4 GB + 0.9 GB = 3.3 GB commit, 1.2 GB under the limit, which is how it ran before the dashboard. With the iframe: 3.3 GB + 0.7 GB = 4.0 GB at load, and 4.0 GB + 0.4 GB = 4.4 GB after a shift, 0.1 GB under the 4.5 GB limit, which is where Windows starts warning. With navigation instead, the peaks are 3.3 GB on the HMI page or 2.4 GB + 0.7 GB = 3.1 GB on the dashboard page, never the sum.

Decision from these inputs: the embedded layout ends a shift 0.1 GB under its limit and will warn; the navigated layout holds 1.2 GB of headroom at its worst and will not.

Two changes that look like fixes but are not #

  • A bigger paging file raises the commit limit, so the warning fires later, and the overflow pages sit on storage orders of magnitude slower than RAM, so the HMI stutters and repaints blank instead of warning. It buys days, not capacity. Use it only as a bridge while you remove the embedded page.
  • A different browser is not on the table. Current browser releases no longer install on a Windows generation this old; the newest build that runs is the one already on the panel, the other mainstream browsers refuse to install, and the one alternative that did install did not render the embedded frame in testing. The operating system is the ceiling, not the browser brand.
  • An operating-system upgrade is a hardware-support question, not a settings change. Chase it only if the panel vendor documents a newer Windows, drivers included, for that exact model; otherwise it is a dead end and replacement is the path.

Separating memory pressure from a tag fault #

  • Values correct and updating while the warning is on screen: capacity problem, so fix the page layout, not the tags.
  • Values missing, frozen or wrong with no warning: follow the tag path, subscription, driver, controller data, before touching memory settings.
  • Warning only while the dashboard page is open: the embedded page is the marginal load. Confirm by opening the same dashboard as a standalone page and comparing commit.

When the panel has to go #

Run the one-page configuration for a full shift and record peak commit on the heaviest page. If peak still rides at or above physical RAM, the visualization no longer fits this panel: cut dashboard content until it fits, or move to industrial panel PCs whose current operating system runs current browsers. When you specify the replacement, size RAM, SSD and Windows for an HMI panel PC against the workload rather than the OS minimum; the commit arithmetic above is the budget method.

Questions asked

Will increasing the paging file stop the warning?

It delays the warning by raising the commit limit, but the overflow pages sit on storage far slower than RAM, so the HMI stutters and repaints slowly instead of warning. Treat it as a bridge for a few days while you remove the embedded page, not as added capacity. If the paging file is system-managed on a nearly full partition, freeing disk space lets it grow on its own.

How much RAM does a web HMI on a panel PC need?

Budget it, do not guess it: operating system and background services, plus the browser holding your heaviest single page, plus room for that page's live-data growth over a shift. If that total stays below physical RAM, the paging file never enters the loop and the warning cannot fire. Run the heaviest page alone, read peak commit from the Windows performance graphs, and add at least 20 percent margin.

Can I keep the dashboard visible alongside the HMI?

Not in the same browser window without paying for both pages. The alternatives are to bring the dashboard's data into the HMI page itself through its own tag bindings, so one page renders both views, or to give the dashboard its own display driven by a separate, adequately sized computer. An iframe always costs the embedded page's full footprint, however it is styled.

Is the virtual memory warning a sign the panel is failing?

No. It is an operating-system capacity message triggered by commit charge, and it appeared exactly when the embedded page was added. Hardware failure on these panels shows up as blank or dim screens, dead touch zones or boot faults instead. If you see those symptoms, you have a different fault; otherwise the panel is healthy and the workload is the problem.

Would a newer browser on the same panel help?

Not on this generation of Windows. Current browser releases no longer install on it, so the newest build that runs is the one already installed, and the alternatives either refuse to install or did not render the embedded frame in testing. The operating system sets the ceiling; only newer hardware running a current OS lifts it.

Keep reading

  • Selection guide

    HMI Panel PC RAM, SSD and Windows Selection Guide

    Order 4 GB of RAM as the default: the documented floor of one size lower suits only a panel running a single lightweight runtime such as AdvancedHMI. Take 128 GB of SSD storage unless logs are small or purged quickly, when 64 GB is enough. Order 64-bit Windows 10, ideally the IoT Enterprise LTSC build, and have RAM, SSD and the OS printed on the quotation before the enclosure is cut.

    Panel PCs and displays

  • Explainer

    Where JavaScript and WebAssembly Actually Run on an HMI

    JavaScript and WebAssembly execute in the HMI client's browser engine — the panel itself, a panel PC, or a desktop browser — never inside the PLC, which only serves the files and exposes data through a documented interface. Decide on the rendering route the installed runtime provides, then verify rendering, module execution, and the data path in that order.

    HMI and touchscreens

  • Troubleshooting

    Getting a Touchscreen Working Under a Linux HMI Runtime

    A loaded kernel module proves only that the kernel accepted the touchscreen driver. Touch reaches the visualization only when the driver exports events the image's input layer actually reads — typically an event device under /dev/input consumed by the Nano-X or evdev layer — so verify each link before editing configuration. If the driver exports no event interface, no configuration change fixes it.

    Panel PCs and displays