search

winder / Universal-G-Code-Sender

A cross-platform G-Code sender for GRBL, Smoothieware, TinyG and G2core.
http://winder.github.io/ugs_website/
GNU General Public License v3.0
1.85k stars 758 forks source link

Dialog Boxes not showing up #2449

Closed N0TB0T closed 3 months ago

N0TB0T commented 5 months ago

Version

2.1.4

Hardware / Firmware

GRBL 1.1

What happened

The dialog boxes for no matter what ("Open File", "Options", ...) won't open. Only immediately after a restart, there's a guarantee they will, but after some clicks here and there, menu items will turn blue/selected when clicked, but nothing happens. Can't run two files after another.

How to reproduce

Can reproduce behaviour any time when running UGS.

Operating System

Windows 10, nothing special at all.

Anything else

No response

breiler commented 5 months ago

Please attach your log file from C:/Users/[your username>]/AppData/Roaming/ugsplatform/var/log/messages.log

N0TB0T commented 5 months ago

messages.log

N0TB0T commented 5 months ago

So I guess it comes down to:

"java.lang.InternalError: The current process has used all of its system allowance of handles for Window Manager objects"

?

breiler commented 5 months ago

Sorry for the late reply.

I have no idea what is causing this error. Similar message has occurred for this user: https://github.com/winder/Universal-G-Code-Sender/issues/2417

I am wondering if dropbox is doing strange things with the files? Maybe try placing UGS in another directory, C:\Users\buddybrand for instance?

N0TB0T commented 5 months ago

There might be some flagging/locking going on in the background, i don't know either. Since moving the files to another location (C:) everything's smooth.Am 07.02.2024 20:41 schrieb Joacim Breiler @.***>: Sorry for the late reply. I have no idea what is causing this error. Similar message has occurred for this user:

2417

I am wondering if dropbox is doing strange things with the files? Maybe try placing UGS in another directory, C:\Users\buddybrand for instance?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

breiler commented 3 months ago

This was likely caused by this issue #2465, fixed in UGS v2.1.6