Output Spam from CoreGui Topbar UI

Bug Reports Engine Bugs
#1

Reproduction Steps

I am getting these warnings spammed in my output every time I run a studio test:

1232×1242 387 KB

This is very annoying, as it slows down programming workflows, especially when this goes on for weeks without being fixed.

Expected Behavior

GoreGui should never emit output in the console

Actual Behavior

A large amount of output from incorrect 9-slice bounds is spammed in the console on any studio test.

Issue Area: Engine
Issue Type: Performance
Impact: Low
Frequency: Constantly
Date First Experienced: 2022-08-22 00:08:00 (-06:00)
Date Last Experienced: 2022-08-22 00:08:00 (-06:00)

1 Like
#2

Additional Information:

This bug seems to happen based on resolution.

Reproduction (For people who don’t have this bug occur already):

  • By clicking the resolution emulator in Studio
  • Click the top bar
  • “Manage Devices”
  • Press the plus at the bottom and put in Width: 3840 Height: 2160 (4K)
  • Then select the device (for me named: newDevice5)
  • Finally click “Play”

You’ll receive the actual behaviour.
Although I’m not exactly sure what resolution begins to produce the behaviour.

image

1 Like
#3

Well, I reproduced it, but it didn’t seem to keep spamming in the output. Just this blob of output shows.

image
image1920×858 100 KB

And then it stops.

It must be over 1440p height, since my monitor has 3440x1440.

1 Like
#5

I only have a blob of input, not spam. Might depend on PC specs

#6

Question to the OP:

Does it keep spamming the output until you stop play-testing or is it just one big blob of CoreGui warns per test?

@SubtotalAnt8185 @JustAGameDeveloper1

I don’t think the OP was meaning that their output is spammed every second with this:

image
image1910×803 140 KB

But rather the blob of CoreGui warn is occurring every time they play-test.

1 Like
#7

Nope; I only see this warning appear once in a playtest. It’s just a very long warning that gets things like errors/ other warnings lost in output

1 Like
#8

Bumping this post, as it’s been 2 weeks now and no response.

Thanks.

#9

Small detail: judging by posts here and my experience, this may only happen when using device emulation in general, regardless of screen size.

1 Like
#10

Thanks for the report! We’ll investigate.

2 Likes
#11

Still occuring to this day. PLEASE fix this roblox.

image
image1350×156 38.9 KB

#12

So, so sorry for the late response. This issue is no longer reproducible, so I’m going to close out the thread. Please refile if you’re still having problems.

1 Like
#13