Open larrytalley opened 9 months ago
Thanks so much for opening up your first issue here on the repository! 🎉 We would like to warmly welcome you to the community behind the app! ☺️ We'll check in soon and have a look at your issue. In the meantime, you can check your issue and make sure it aligns with our contribution guidelines! Here's the comprehensive list:
NOTE: Please do not share screen captures of buggy behavior on YouTube. If you have uploaded a video on YouTube and linked it already, don't worry! But, we would like to ask you to remove the video from YouTube and upload it directly to GitHub instead, by editing your comment. Read more here.
An enhancement takes a feature and improves or alters its behaviour. Please make sure to argue how your proposition will aid non-technical text workers, and why it can't be emulated easily with other features or apps!
Feature requests introduce whole new features into the app. This requires a lot of work, so these might be turned down if the implementation costs supersede the benefits we expect to see from implementing it. Please do not be disappointed if that happens. It likely has nothing to do with your great request but simply with us and our missing resources!
You can of course always ask someone to implement this feature, because a PR with a working new feature has much higher chances of being merged! :)
Please note that one of the main reasons for why bug reports cannot be addressed is that there's not enough information for us to find and fix the bug you describe, so make sure you try to pinpoint the bug as close as possible.
The ideal bug report for us has two qualities:
Please note that if you encounter behaviour that does not align with your expectations of what would happen, this might as well be simply intended behaviour and we need to simply clarify why the behaviour is the way it is. This is not to be considered a bug and such issues may be closed! Suggest an enhancement instead!
But now, have a great day and thank you again!
Another aspect of the issue: when I press the + to create a new issue, it is a very long time before a new item "window" opens up, but, then when it finally does appear on the screen -- if I jump right in and enter some text, and/or paste some text -- then often I have entered it too early, and the text just entered will be wiped out as some additional task completes and the new item is finally actually "ready" to accept new text. This happens often enough that I am sure I can reproduce it every time by being quick to enter, but, in normal use it doesn't always bite me because I've learned to give the new empty window a bit of time to become ready. But when it does bite me, I see the text appear in the newly created window and then suddenly the window is empty again. After the text I entered quickly is wiped out, this does not happen again, i.e., once the window is really ready to accept text then it behaves normally for subsequent text entries.
So, first of all, neither your amount of files nor the amount of Zotero items directly should cause such a slowdown. I have more than double the amount of files and for me, it's working snappy. From when is your MacBook, if I may ask? Especially old ones may have become a bit slower over time.
Finally, maybe a screen capture might give me more of a sense as to what exactly is then causing the slowdown – as I said I can't imagine a specific reason right now, but seeing how everything loads might give me a clue as to where it might come from.
What do you want me to capture with a screenshot? Trying to anticipate, I started Activity Monitor, focused on Zettlr, and took a screenshot of Statistics, below. Does it strike you as odd that I am using 1.13 TB of virtual memory?
While I was watching (i.e., had Activity Monitor up) it performed reasonably. But I haven't been doing much in Zettlr today. I'm thinking that perhaps a garbage collection ran and cleared things up, or something. I fully expect that if I get back into steady usage, where I am actively researching via Chrome, then I find things, click the Zotero button to capture a citation, add an item to Zettlr and name it based on the new fact, then copy from the screen or a download, and paste into Zettlr, then reference the citation by adding the markup and the new Zotero Citation Key... if I start doing that persistently I think I can bring Zettlr back down to a crawl. But I won't know until I try it. Perhaps I'll get back on it tomorrow.
So, I don't know where the 1.1TB comes from, but that looks like a bug in the monitoring tool -- macOS would've already killed the app if it really used that much. There must be something else going on. What I was hoping for is really just a screengrab, just to confirm what's going on. Because right now it's difficult to see where it might be caused.
I'll upload a screenshot from m y current work.
I also used the Mac Activity Monitor to "sample" while Zettlr seemed to be in suspended animation. I had just returned to Zettlr, bringing it to foreground, and was attempting to click in the search term field but my mouse clicks were being ignored (or queued maybe.) So I brought up the Activity Monitor and clicked the Sample control. Here is what was captured:
Ah, I meant a screen recording (not a static image) so that we could see where the slowdowns happen precisely. Also, I wrapped the stack trace into an HTML tag so that we don't have to scroll for hours to view newer comments. That sampling is unlikely to help us, though.
Ha, makes much more sense, I should have known what you were asking for. I'm old school, still thinking in terms of a tty. Ok, I've made a recording.
https://github.com/Zettlr/Zettlr/assets/8377009/a73395f6-e700-4db4-9b0c-68464343af03
when hit hit return on the title of the item i began typing digits at about 1 per second, so you can see that it was 3 seconds before it was even queuing my keystrokes, and 4 seconds before the display began showing my input.
this isn't too bad, much better than it sometimes is.
still kind of discouragingly slow.
The performance so far today is completely usable. But the day I opened the ticket, when it was taking most of a minute before I could enter text into a new item, that wasn't really usable long term. I'm glad it is better now, I wish I knew what makes the difference so I could reproduce the "speed up" when I need to.
Is there an update or solution to this bug report? I can confirm the very slow performance of version 3.1.1 on macOS version 14.4.1 (M2) when keying in a keystroke, changing tabs, or opening a document. As a workaround, I only open very few tabs.
There is a solution as soon as this issue is closed. As of now, I am unable to reproduce (have ~3,000 files and can open 50 tabs with no issue, MBP 14in M2 Pro), and that means that I don't know where the issue may be. Could be very well something in the computers configuration, but as I said I don't know.
My current workaround is to close Zettlr and re-open it when the problem gets really bad. It seems to be faster when it has been recently restarted.
Description
I got fond of Zettlr and now have 1166 items. I have Zettlr Version: 3.0.5 (UUID: 7f1e155e-93ca-4c36-b780-197d80a0c859) System: darwin 13.6.3 (architecture: x64)
I'm using Better BibTex with automatic export from Zotero to manage citations and have about 13,000 items in Zotero.
Zettlr slowness manifest badly when I create a new item, it often takes up to a minute before I can start entering into the new item. And if my entry is a paste, sometimes nearly a minute between pasting and seeing the content in Zettlr. I would be glad to turn some features off if I could, for example the "related files" pane, if I knew how, and if that would help the performance. I don't know when the performance got so bad, it must have happened slowly over time, I don't associate the performance issue with a particular update or any other change I can recall.
I would be happy to insert debug info if I knew how to generate something useful.
Reproducing
It happens now every time I create a new item, and probably every time I paste into a newly created item.
Zettlr Version
Stable (most recent version)
Specify version
3.0.5
Installation Method
From the Website or GitHub
Your Platform
Architecture
Operating System Version
Ventura 13.6.3
Additional Information
No response