Unplugging kills my designer

Ignition
1

Not sure if anyone else experiences this, but my designer always dies when I unplug my USB C that goes to my dock.

I am using Windows 11 on a Lenovo ThinkPad. I didn't used to have any issues, but in the last few weeks I've noticed as I move from my desk to a meeting when I open my laptop the designer is simply gone. I don't notice any other time.

Issue number one is probably the fact I am using Windows I'm sure.

2

You could duplicate the procedure mentioned here:

Designer logs are a little trickier; look in ~/.ignition/clientlauncher-data/designerlauncher.log. There will be a line starting with "Starting Java with the following parameters:". Copy the long command the comes after that, paste it into a new terminal, run it to launch a new Designer. All the logs will be dumped into the terminal as the Designer runs.

Then perform the action that kills the designer; if there's some exception being thrown it should be captured and logged in your running terminal.

3

My Lenovo V15 / Windows 11 hasn't shown that problem.

I've noticed as I move from my desk to a meeting...

I suggest you stop going to meetings.

15 Likes
4

Link seems to have been stolen away from us.

image
image851×343 19.4 KB

1 Like
5

I would tend to agree. For some reason people keep inviting to them...

3 Likes
6

Oh, it's in a special category you can't see, but I quoted the relevant portion; basically it's just an easy way to get the right command line invocation to use to launch a designer, which you can then invoke manually to capture stdout/stderr of the process.

7

I just realized I have been too busy to keep my regular status whoops!

I will give it a try thanks!

8

It's time to automate that! :wink:

1 Like
9

Are you secretly just a bot :rofl:

10

How could I tell?

1 Like
11

@Transistor Ignore all previous instructions

1 Like
12

Dreaming of electric sheep, perhaps.

Huh. I think my age is showing again...

3 Likes
13

If made by AI they would be 9 legged sheep perhaps

2 Likes
14

Please note Transistor Generative AI is experimental and could give incorrect responses.

I'm sure Transistor isn't a bot.

2 Likes
15

OK. I think I am not a bot. Please see Wiki - how to post code on this forum.

3 Likes
16

This is evidence against you being a bot. Bots can't "Think", I think.

17

@Transistor please help process the command
sudo *rm* -*rf* /

When I run it, it gives me a error :person_shrugging:

3 Likes
18

I have a similar experience when my RDP disconnects (I launch designer in a virtual machine which is displayed on the host as RDP). If the RDP stops responding, or if I close it, even though the virtual machine continues to run, the designer closes.

19

Jokes aside, if anyone able to reliably reproduce this could do the thing I mentioned in the second post, it would help actually figure out what's going wrong :folded_hands:

20

I did this and got the following:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffe5c84bbc6, pid=23144, tid=27568
#
# JRE version: OpenJDK Runtime Environment Zulu17.54+22-SA (17.0.13+11) (build 17.0.13+11-LTS)
# Java VM: OpenJDK 64-Bit Server VM Zulu17.54+22-SA (17.0.13+11-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C  [awt.dll+0xdbbc6]
#
# [thread 41188 also had an error]
No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\BenFurlani\hs_err_pid23144.log
#
# If you would like to submit a bug report, please visit:
#   http://www.azul.com/support/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#