Critiques pour Correcteur de texte - LanguageTool
Correcteur de texte - LanguageTool par LanguageTooler GmbH
4 851 notes
- Noté 5 sur 5par Utilisateur ou utilisatrice 19839761 de Firefox, il y a 5 heures
- Noté 1 sur 5par Utilisateur ou utilisatrice 13477865 de Firefox, il y a 14 heuresCauses a memory leak.
- Noté 5 sur 5par Tanxowski, il y a un jour
- Noté 5 sur 5par Utilisateur ou utilisatrice 19834494 de Firefox, il y a 3 jours
- Noté 5 sur 5par oichtental, il y a 4 jours
- Noté 5 sur 5par Wilf, il y a 4 jours
- Noté 1 sur 5par Iori, il y a 6 joursThis is an evil extension!!! Why? We have been scratching our heads to find out why there is a consistent memory leak issue. It has wasted a lot of our precious time! Moreover, we even consider adding more memory but the memory price is very high now! We have never felt such pain in recent years! We are very angry that this poor plugin is so popular and has not fixed this issue in the shortest time.
- Noté 4 sur 5par Wimpers, il y a 7 jours
- Noté 5 sur 5par H2O, il y a 9 jours
- Noté 5 sur 5par Utilisateur ou utilisatrice 12775409 de Firefox, il y a 9 jours
- Noté 1 sur 5par Virtpunk, il y a 9 joursA huge thank you to the person who wrote a review below. I've been using this extension for five years, and in the latest version, either there's an unintentional bug, or the developers intentionally introduced a leak that hadn't existed for 10 years.
This extension is currently causing a memory leak in the browser, even when I'm not opening anything and only on one page. It reaches 60 gigabytes for me, after which everything in the OS starts crashing with errors, from the browser to other programs.
I've been racking my brains for 2-3 weeks of torment, I couldn't figure out what was going on, because I've been using all the extensions for years and everything has been working without a hitch for a long time.
And it turns out that's what it is. The extension, which had been reliable for years, is now leaky and buggy, leaking 40-60 gigs of memory.
As soon as I removed this extension, everything has been fine for several weeks now. - Noté 5 sur 5par MohamedSubarashi, il y a 11 jours
- Noté 5 sur 5par Russ Brown, il y a 12 joursMuch more through and intuitive than any other grammar and spell checker I have used.
- Noté 5 sur 5par MaB, il y a 16 jours
- Noté 5 sur 5par Utilisateur ou utilisatrice 18062762 de Firefox, il y a 18 jours
- Noté 4 sur 5par Jed, il y a 18 joursThis is a great tool, however it needs some improvements. The button that is displayed when the user types in the text field, overlaps with the button displayed by another add-on - "DeepL: AI translator and writing assistant". Can this be fixed?
- Noté 5 sur 5par Utilisateur ou utilisatrice 18660826 de Firefox, il y a 24 joursI like that it still allows custom sources.
- Noté 5 sur 5par Utilisateur ou utilisatrice 17472807 de Firefox, il y a 24 joursReally nice, and for me at least, it even seems to be free!
- Noté 5 sur 5par obook, il y a un mois
- Noté 5 sur 5par kip, il y a un mois
- Noté 1 sur 5par Voytash, il y a un moisI’ve been using LanguageTool for over 2 years and I really liked it — until about a month ago.
Recently, the extension started causing extreme RAM usage while typing. I have 32 GB of RAM, and during normal use I sit at around 18–20 GB. However, as soon as I start typing in a text field where LanguageTool is active, memory usage quickly spikes to 30–32 GB within seconds, which often leads to Firefox freezing or crashing completely.
This happens multiple times a day. In some cases, just 10–15 seconds of typing is enough to crash the browser. I even had to start writing messages in external apps (like Notepad) and then pasting them, just to avoid crashes — which completely defeats the purpose of using this extension.
What’s strange is that:
- this problem only started about a month ago,
- before that, I had zero crashes for over 2 years,
- I didn’t notice any recent updates that could explain this behaviour.
At this point, the extension has become unusable for me due to its massive resource consumption.
That said, aside from this issue, I really liked LanguageTool and I hope this gets fixed soon.