Zotero.exe Application Error - Memory Reference Issue

Younes.ab
I encountered an error message when attempting to open Zotero after updating to Zotero 7 . The error message states:
The instruction at 0x00007FFEFDF4C4AA0 referenced memory at 0x000000000001240. The memory could not be read.
Report ID 802098886

After closing this error window, Zotero seems to work normally. However, I am concerned about this recurring issue and would like to understand what might be causing it.

I would appreciate any guidance on how to resolve this issue or whether it can be safely ignored. Thank you!

https://s3.amazonaws.com/zotero.org/images/forums/u13360471/vkupepsxv558ahieyn8p.png
  • dstillman
    If you get it again, uninstall Zotero and reinstall it from the download page, and let us know if it happens again after that.
  • Younes.ab
    I store files locally not in cloud , does reinstalling will affect my data?
  • dstillman
    No
  • Younes.ab
    Thank you for your help i will try reinstalling it ,, i think its the same for plugin they will be installed automatically after?
  • Younes.ab
    The issue persist even after Reinstalling Zotero
  • Younes.ab
    I want also to add that when opening pdf file zotero becomes slows and couldn't even highlight text , the issue is related only to zotero , other application works normally .

    laptop specification : Intel Core i7-1165G7, NVIDIA GeForce MX450, 16GB RAM
  • dstillman
    I don't recall any other reports of this throughout the entire Zotero 7 beta period, so this is likely caused by something else on your computer. It could be your NVIDIA drivers/settings or some other software. You should try updating everything and disabling any other system utilities you're running.
  • jerryhu0901
    I am experiencing this same issue, did you by chance have fixed this?
  • Younes.ab
    I appreciate your earlier response, but I have to express my frustration. Dismissing this as a problem with my system's drivers or settings feels dismissive, especially now that I've confirmed another user is experiencing the exact same issue.

    This is clearly not an isolated case, and I strongly urge you to investigate this as a potential issue within Zotero 7. It’s important that this matter is taken seriously and not just brushed off as a problem with individual configurations.

    I trust that you will take the necessary steps to address this issue.

    and unfortunately, it hasn’t been resolved yet.
  • jerryhu0901
    my solution is to just go back to zotero 6 and no such error shows up anymore...
  • dstillman
    @Younes.ab: Unfortunately there just aren't any steps we can take. It's a generic error without enough information to debug it and we can't reproduce it ourselves, so we'll need someone who can actually reproduce it to try to figure out what on their system is causing it to happen. It didn't come up during the year-plus-long beta period for Zotero 7, and we've received a total of two reports since releasing 7.0, so it seems to be very rare and limited to some specific system configuration.

    If you can't figure it out, some future Zotero update might be fix it — Zotero is based on Firefox, and we periodically update to a newer Firefox base, which could potentially fix this sort of thing — but I'm afraid that's all I can tell you at the moment.
  • dstillman
    @Younes.ab: To clarify, you see this on every Zotero startup? And then you close it and Zotero works normally?

    Can you provide a Debug ID for Zotero startup through reproducing this, using the "Restart with Logging Enabled…" option? We'd want the last bit of the log while the alert is still showing, so if you can't submit the log while the alert is open, you can take a screenshot of the log window and share that instead.
  • dstillman
    @jerryhu0901: Same question for you, if you want this fixed.
  • Younes.ab
    Yes, I see this issue on every Zotero startup, but after closing the alert window, Zotero works normally.

    The issue first appeared after I installed the 64-bit version. I tried reinstalling the 32-bit version afterward, but the problem persisted. The Debug ID is D1565463107.

    Let me know if you need any further information.

    Thank you for your support and the time you're taking to help resolve this. Let me know if you need any further information.

  • Younes.ab
    I've also noticed that Zotero becomes very slow when reading PDF files. While the EPUB reader works fine, PDFs are significantly sluggish. For example, it takes 5 to 10 seconds to select text when trying to highlight something in a PDF. The same delay occurs when trying to go to the next page.

  • dstillman
    edited August 16, 2024
    Start by disabling all plugins. Does this still happen?

    If so, we'd want to see another Debug ID from startup for that. Also make sure you're submitting the output while this alert window is still open.
Sign In or Register to comment.