When using neo4j, Imaging sometimes becomes unresponsive with slow rendering and loading of the graph. This may result in a blank browser page, or "Something went wrong while displaying this webpage" error or "This page is having a problem" or a "Page Unresponsive" error.
This issue is usually seen when the number of components or links between the components are more.
Solution
- Check whether the memory for Neo4j is set based on the instructions in Optimize Neo4j memory allocation.
-
Check if the issue is with the browser memory. Try to increase the browser memory and test it.
eg for Edge increase the JavaScript heap memory limit to 4GB (adjust the number as needed).
- Locate the Edge Shortcut.
- Right-click the Microsoft Edge shortcut on the desktop or taskbar.
- Select Properties. Modify the Target Path:
-
In the Target field, add the following flags after the msedge.exe path:
--max-old-space-size=4096default path :- "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --max-old-space-size=4096
-
Check the graphics memory VRAM of the VM/server in the DirectX Diagnostic tool. If it is 0 it means there is no dedicated graphics memory (VRAM), and all the rendering tasks is handled by the CPU and system memory. This can severely affect performance, especially when dealing with complex graphical rendering.
The following solutions, can then be tried.
- Upgrade the server's graphical hardware.
- Verify and update the graphical drivers.
-
If using a VM , try to access the Imaging URL from outside of the VM in a server with sufficient VRAM, then check if proper graph rendering is taking place.
NB: VRAM should be increased at least by 10%, more than the total memory.
Related Pages
Hardware requirements for CAST Imaging WithAIPConsolev.2.x
Optimize Neo4j memory allocation.
CAST Imaging - Configuration process - Memory configuration - Neo4j service failed
Tickets
51809, 53650, 49679, 51777, 51848
Comments