Black Screen Issue When Displaying Code Boxes in Playground

API Bugs
1

Hi everyone,

I’m experiencing an issue with the Playground feature. When code snippets are displayed in the black boxes, my screen goes completely black, and I have to refresh the page to get it back to normal. This happens only with the code boxes, regular text messages work fine.

I’ve tried clearing cache and cookies, disabling browser extensions, and switching to a light theme, but the problem persists. I’m using [your browser] on [your operating system].

Has anyone else encountered this issue? Any suggestions or solutions would be greatly appreciated.

Thanks!

8 Likes
2

I’m getting the same issue. Seems like it is only when a code box is displayed. The screen goes black and I have to refresh. I’m using Chrome on windows 10.

1 Like
3

I believe it is a system error, I am using the Brave browser on Windows 11, I have tested other browsers and the same error continues, I have been using the assistant for so long, this has never happened, I hope they fix it soon.

2 Likes
4

Same here, i get blank screen until refreshing screen. Refresh only works if the response has been completed, otherwise the screen comes back but response is blank, wait a bit for it to finish, refresh and it’s all there. So annoying when you have to wait after ever prompt. Please fix this OPEN AI and don’t just ignore it as usual.

3 Likes
5

I am having the same issue with Edge. I hope this can be resolved soon.

1 Like
7

I’ve already changed to Lama 3.1 and it’s helping me a lot. In my opinion, I won’t go back to using OpenAi.

1 Like
8

I have experienced the same “black screen” issue in Playground too. It isn’t limited to code blocks. It seems to happen for large input tokens for me.

What happens is you get a black screen after generating an answer. The only way out is to refresh.

2 Likes
9

I’ve been encountering this issue for at least 1 week. This makes the UI assistants totally unusable. And this is a paid service. I wonder why nobody is looking into a fix or workaround for this.
I have this issue in Chrome, tried incognito and no solutions. Tried Firefox and same issue there too.
The only way I could get some sort of answer was through a Postman request.

2 Likes
10

I’ve also been noticing the behavior. When I enter a thread message, the entire screen goes blank. Its consistent across the three browsers I use (chrome, safari, edge). My solution was to just start interacting via API a whole lot more. Hoping it gets fixed though.

1 Like
11

I have experienced the same strange behaviour since yesterday. It looks like this: https://youtu.be/P5asKb1PHnU

1 Like
12

Experiencing the same issue, so frustrating.

1 Like
13

I’m experiencing the same issue, UI is unusable at this state.

1 Like
14

Still replicated every time. Possible workarounds:

  1. Use the API with Postman as mentioned above
  2. After black screen shows up wait a few seconds then copy and paste the thread url from the browser tab into a new browser tab.
15

I’m using NextChat for Windows with my ApiKey, life saver.

16

This is still an ongoing issue. No response from OpenAI in 2 weeks and prevents playground from being used in a productive way for coding/infrastructure work.

17

FIXX FOUND

I know its not ideal, but its also a very quick fix.

Top of the chat, on the right side click the GEAR icon.
Disable ‘Stream Responses’

Just wait til the output is finished and no refreshing needed <3

2 Likes
18

Much appreciated, I ended up swapping completely to a different AI due to this issue being so obnoxious for me. This setting did work!

20

Now every prompt instanly blanks the screen for me and it’s unable to recover. If you go to the thread in dashboard and click on the thread that crashed to see the thread detail, the screen goes blank as well, this is ridiculous. I turned off streaming and it doesnt do anything.

Edit, as I was typing this, i realized it’s because i used triple ``` to enclose a block of code in my prompt. I took those out and turned off Streaming and now it works again, WTF?

21

I brought this up to OAI today.

The only workaround is to use the API and not rely on Playground, especially for large token jobs, until this gets fixed.

2 Likes
24

Yep, worked. Thanks, I’ve been “refreshing” the screen with the thread for weeks now.