Codex crashes and gives a white screen after 10 mins of use about codex HOT 14 CLOSED

I've also had this happen to me - mostly when I'm actively taking notes and not when I'm only reading through my notes.

from codex.

I've also had the same thing, using windows 10.

Not sure if anyone else has had the same problem, but codex seems to be far more laggy compared to pre 2.0
This is especially noticeable if you start to type even slightly faster, you'll notice that codex will become super slow, and you'll have to wait for it to finish inputting the characters.
I use a microsoft surface with 16Gb of RAM and I have a desktop with 32Gb of Ram, and have the same issue on both, so it's not a lack of memory thats the issue.

When codex starts to slow down, the memory usage definitely begins to climb when looking at task manager. However, once it crashes, it is no longer using memory (duh it just crashed). CPU usage and GPU usage remains relatively constant.

If you continue typing after codex begins to slow down, and just keep performing actions, then codex will crash. However, if you just give it a second to catch up, it won't crash, but it certainly degrades the user experience having to wait like 5-10seconds for a sentence you just typed to slowly appear on the screen.

I've reverted back to using 2.0.0 from 2.0.1 and although the issue is still there, it seems to be less intense.

@jcv8000 I'll force a few crashes and upload the log files in the next coming days

from codex.

I just uploaded 2.0.2, that should hopefully fix most of these issues. Please try it out and let me know if you're still having any of these issues

from codex.

I'm honestly relieved to see that it's not just me experiencing this. I'm having all the issues described above, including the program slowing down for image-dense files.

I also tried to force the white screen a few more times, but got nothing in the logs folder.

from codex.

@jcv8000 you're an absolute legend mate, as far as I've noticed ever since updating the issue seems to be resolved

Happy days, happy days indeed <3

*edit
@ThatOneGuy36 can mark this issue as resolved now, unless anyone else is still having trouble

from codex.

After thoroughly using the latest version of Codex, I personally have not experienced any problems. Seems like the fix did the trick!

Thank you @jcv8000 for that!

from codex.

Agreed, problem solved, thank you @jcv8000!

from codex.

I love this app. My friend who uses a Mac told me he had this problem as well after I recommended this to him.

from codex.

@dulocian @JesseGuerrero @ThatOneGuy36

Thank you all for reporting this. So it sounds like this is happening on all platforms then

When this happens can you check Task Manager (or whatever it is on macOS) and see if the app's memory usage starts expanding over the time it's running until it crashes?

There's a new logs folder in the app's default save folder (%APPDATA%/codex on windows, ~/Library/Application Support/codex on macOS), are there any errors appearing in there when the app crashes?

from codex.

I absolutely love this app! Sadly, I don't have this issue with Windows 10 to give logs. Hopefully one of you can do it.

from codex.

So I've been messing around a fair bit, and here's what I've found.

It seems that opening and switching to files that have images, and trying to type into those files will cause codex to lag (very noticeably)
But if you switch to a file that doesn't have any images, there appears to be no lag.

If you want to replicate this, just create a folder, and put 3-4 pages in there, type random stuff and throw a few images into 2-3 of the pages, and in the last page only have text.
Switch between the pages with multiple images and text, and then back to the page with only text.
You should notice the lag when trying to edit larger pages with images, as opposed to the page that is just text.
(also don't forget to save the pages, seems to be fine if the pages are unsaved)
[note: its not consistent, i've done it a few times and results definitely vary with no apparent common factor]

After managing to force 2 crashes, there's still nothing in the log folder.
How am I defining a 'crash': when codex is no longer responsive, and simply turns to a white screen.
[its more frozen than crashing]
Then i just have to force quit it using task manager

The developer tools button also doesn't work so not sure how to provide any error messages.

I really love this app and definitely hope this gets resolved, bc its by far and wide my favourite tool and would love to see more people get their hands on it and love to use it just like I do :))

from codex.

Wow, I experienced this for the first time. Interesting. Yea, I got a white screen.
OS: Windows 10

from codex.

The same issue happened with me just 5 minutes ago. I had a single Notebook with 5 pages in it. The lag started when I created my 4th page and on the 5th page, when I had written about 15-20 words I noticed the lag got pretty serious and the screen turned white.

I quickly looked at the Task Manager and I did not see any anomalies when it came to resource hogging.

When it comes to the bare metal of my machine, 16GB of RAM is more than enough.

OS: Windows 11
Codex version: Latest (2.0.1)

from codex.

Awesome to hear, thank you all for your help reporting and resolving this. I'm going to go ahead and close the issue 👍

from codex.