Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Render process gone if a too big Json has been pasted into a new note #10564

Closed
Wolle181 opened this issue Jun 11, 2024 · 7 comments
Closed

Render process gone if a too big Json has been pasted into a new note #10564

Wolle181 opened this issue Jun 11, 2024 · 7 comments
Labels
bug It's a bug stale An issue that hasn't been active for a while...

Comments

@Wolle181
Copy link

Operating system

Windows

Joplin version

2.14.22 (prod, win32)

Desktop version info

Joplin 2.14.22 (prod, win32)

Client-ID: 10d96d0d427f45e3b9e098bd65721e5c
Sync-Version: 3
Profil-Version: 46
Unterstützter Schlüsselbund: Ja

Revision: e579eb9

Backup: 1.4.0

Current behaviour

  1. Open desktop app
  2. Create a new note
  3. In notepad++ or VSC, have a big json file in prety print format (in my case, 2 mio lines, ~60MB) and copy it into clipboard
  4. In the new Joplin note, press Ctrl-V to paste it

Expected behaviour

Json will be shown or at least a message indicating "too big to show"
Instead: Shortly after pasting, a message box appears: "Render process gone" wiht optino to restart in safe mode.

Note: At my second attempt to reproduce this behaviour for this bug report, I could delete the too big note, but initially when this first happened, deletion was not possible even in safe mode. Deleting the .config dolder and re-sysnc solved the problem.

Logs

joplin_crash_dump_20240611T123833.json

The reproduction of the error occurred at 14:38:27 in the log ("textPaste").
log.txt

@Wolle181 Wolle181 added the bug It's a bug label Jun 11, 2024
@laurent22
Copy link
Owner

Does it work any better if you select the Beta editor from the options first?

@personalizedrefrigerator
Copy link
Collaborator

At least for me (beta editor), I can get Joplin to run very slowly after pasting Joplin's yarn.lock several times (24,803,840 characters), particularly when the note viewer is visible. I haven't tried with anything larger.

Copy link
Contributor

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@github-actions github-actions bot added the stale An issue that hasn't been active for a while... label Jul 12, 2024
@Wolle181
Copy link
Author

Wolle181 commented Jul 15, 2024

I retested this issue in version 3.0.13 with opted-in Beta Editor but it still did not come back really. Instead, a popup appeared which informed "Error occurred: Windows does not answer" (translated by me from German) and asked to either close, ignore or restart in safe mode.

The good thing was that when restarting in safe mode, I was able to delete the new oversized entry which lead to the problem and after that could continue normally.

I think a solution could be restrict the size of the Json or switch off auto-formatting for too big content (as VSC does).

(The problem is not a major issue for me and I would prioritise it down. Anyone who has synchronised with WebDAV or made regular backups should be able to cope with it. )

@personalizedrefrigerator
Copy link
Collaborator

#10678 might also help with this.

@github-actions github-actions bot removed the stale An issue that hasn't been active for a while... label Jul 16, 2024
Copy link
Contributor

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@github-actions github-actions bot added the stale An issue that hasn't been active for a while... label Aug 15, 2024
Copy link
Contributor

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug It's a bug stale An issue that hasn't been active for a while...
Projects
None yet
Development

No branches or pull requests

3 participants