#VsCode (Cursor) extension seems to have got really slow

1 messages · Page 1 of 1 (latest)

hexed linden
#

Checked out the exstension last week when released and love that I can review before creating my PR's but it seems to really slow my vscode down (MBP m4 24gb so shouldnt be a problem) but clicking the comments on the left code rabbit pane is quite slow and laggy to load the comments

hexed linden
#

Update it sometimes crashes my cursor window

upper crypt
#

yes, please make sure you have the latest version of the extension

hexed linden
#

still slowing down my cursor and occasioanlly crashing, not even when running a review

#

uninstalling code rabbit extension sped it back up

upper crypt
#

Did you try installing the update?

cursive galleon
#

Hey @hexed linden . Sorry you are facing this issue. What is the size of the project you are working on? As in how many files overall

hexed linden
#

a very large monorepo, but really it shouldn't matter as would only be looking at diffs?

curso has no problem indexing/reading context of the repo though

#

uninstalled it at this time, happy to try later as when it first launched was v good

cursive galleon
#

Yeah ideally it shouldn't. I will take a look and let you know once this is fixed.

hexed linden
#

it might be a recent change as it worked v well at the begining of the vscode extensions release

cursive galleon
#

Were you using the extension in beta as well?

hexed linden
#

hmm no how do I do that?

cursive galleon
#

No was curious if beginning meant the beta we had or the release

cursive galleon
#

Hey @hexed linden We have optimized a few things to speed up the extension. The version is 0.7.11. Do try it out and let me know if you still face the issue.

hexed linden
#

Awesome really appreciate the follow up, on holiday atm but will do and lyk

hexed linden
#

unfortunatley not

#

click start review, shows the begginging rainbow spinner then crashes cursos

#

when restarted it says previous review was cancelled

#

is there a way to see the logs?

#

was rly good when I first tried it with cursor on this codebase

#

hmm okay running in vscode seems to work

#

might be cursor specific, or perhaps need to log out and in again "fresh setup" of coderabbit extension, despite uninstalling nad reinstalling it doesnt re prompt to login on cursos

#

nope tried logging in and out of coderabbit on cursor and resetting it and cant get it to work, but works v well on vscode

cursive galleon
#

Okay, thanks for mentioning that, I might have an intuition as to why it's weird in cursor. I will get back to you.

cursive galleon
#

@hexed linden When your cursor crashes, can you grab a screenshot of console in developer tools. Just to nail down the issue.

hexed linden
#

might need a little explanation of how as it just closes and im on my mac desktop

cursive galleon
#

Need to see if there are any errors in your console. Might be some commands being executed in a sub process, but I doubt that. Try running a review with the console open once and let me know.

hexed linden
#

I dont see anything in the coderabbit console on vscode nor cursor

#

assume this is where you're meaning

cursive galleon
#

No, under help -> Toggle developer tools -> Console

hexed linden
#

nothing is logged in the console it crashes before then

#

however

#

created a fresh vite project in cursor and used it fine so must be smth to do with my repo (a work repo being mega)

#

so nws

hexed linden
#

other than logging out and uninstalling the extension is there a harder way to reset the coderabbit to factory on my cursor as when first installed it worked nicely

hexed linden
#

actually got an error code this time

hexed linden
#

yeh still get that error just re tried code rabbit with latest version on cursor and still get that

#

vscode too

#

with dev tools open

cursive galleon
#

Does it still happen on only huge repo or any kind. I haven't been able to reproduce it. If you can give me an open source repo on which it happens, i can try it out.

hexed linden
#

will look for a large enough OS repo to test later this eve, it didnt have issues on this repo (size negligible change) in the first release months ago