Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Console & Visualizer Freezing ~30 commands into job #1844

Closed
caswal opened this issue Mar 26, 2022 · 10 comments
Closed

Console & Visualizer Freezing ~30 commands into job #1844

caswal opened this issue Mar 26, 2022 · 10 comments

Comments

@caswal
Copy link

caswal commented Mar 26, 2022

Version

2.0.11

Hardware / Firmware

GRBL 1.1

What happened

After starting a job, after about 20-40 commands or so. The Sent status becomes stuck "Send Status: (18/357)". The console stops updating, and the visualiser no longer updates either. The time/estimated time still updates.

Commands are still being sent in the background, so the job completes, so nothing is lost. Which is nice.

Stop, Pause buttons no longer work. Can Disconnect, but can't reconnect.
Program can be "Closed" but remains open in background. Still holds lock on the comm resource and must be killed in task manager.

Log Attached. Occurs everytime on this setup.

messages.log
SysInfo.txt

How to reproduce

Occurs every time on this setup. Just start a job, and occurs within the first 40 commands or so.

Operating System

Attached msinfo32 dump above. Win10 Build 19042. HP Thin Client T630 4gb ram.

Anything else

No response

@chrisla23
Copy link

Have you tried increasing your java heap size?

Linking to this as it is a well-written article, not CNC specific:

https://www.bobscnc.com/blogs/troubleshooting/troubleshooting-increasing-ugs-memory

-Chris

@breiler
Copy link
Collaborator

breiler commented Mar 27, 2022

Thanks for the the great bug report. Like @chrisla23 mention it seems that the software has run out of memory.
I can see that you are rotating the model (left then right), does this still happen if you don't do that?

The article that @chrisla23 linked to shows you how to set the minimum size (the amount of memory that UGS should start with). You could try to increase the maximum size from 512Mb to 1024Mb by adding -J-Xmx1024m

@caswal
Copy link
Author

caswal commented Apr 2, 2022

Thanks for the prompt reply. Weekend again so have a play.

Using the bobscnc guide, increased the memory from the default 64m in the conf up to 1024m. Task manager reports it using 750mb. Problem still persists, but does happen later. 90-400 command.
I am using the 32bit version. I'll give the 64bit a go tomorrow.

@caswal
Copy link
Author

caswal commented Apr 2, 2022

A bit more machining this morning. I redact my previous statement. No improvement, is still generally freezing 20-40 commands in.

@breiler
Copy link
Collaborator

breiler commented Apr 9, 2022

Did you set the -J-Xmx1024m?
The instructions in the bobcnc guide are wrong...

@hovercraft-github
Copy link
Contributor

@caswal Can you report the JVM build used please? - it can be seen via UGS About window.
For me, similar issues occur when I run UGS with any JVM build but AdoptOpenJDK-13.0.1+9

@breiler
Copy link
Collaborator

breiler commented May 2, 2022

@hovercraft-github it was run using the bundled Java:

Log Session: Sunday, March 27, 2022 at 11:54:35 AM New Zealand Daylight Time
System Info:
Product Version = Universal Gcode Platform 12.2-d73d3dd898acc440c460924dabf8ad5feb90369f
Operating System = Windows 10 version 10.0 running on x86
Java; VM; Vendor = 13.0.1; OpenJDK Server VM 13.0.1+9; AdoptOpenJDK
Runtime = OpenJDK Runtime Environment 13.0.1+9
Java Home = C:\ugsplatform-win\jdk\jdk-13.0.1+9-jre

@hovercraft-github
Copy link
Contributor

@caswal Yes, this JVM should be alright.
Just for curious: can you reproduce this issue when Visualizer window is closed?

@caswal
Copy link
Author

caswal commented May 2, 2022

Apologies, I 'fixed' it by replacing windows with Ubuntu Mate.

@breiler
Copy link
Collaborator

breiler commented May 2, 2022

Thanks for the feedback.
Closing as we couldn't reproduce the error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants