Skip to content

Casey Truelove

← Adobe Illustrator

My feedback

1 result found

  1. Can't finish previewing. Could not complete the requested operation.

    742 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    447 comments  ·  Illustrator (Desktop) Bugs » Rendering Issues (GPU, CPU)  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Casey Truelove commented  · 

    I'm running an iMac (Retina 5K, 27-inch, Late 2015)
    Processor 3.3 GHz Intel Core i5
    Memory: 32 GB 1867 Mhz DDR3
    Graphics: AMD Radeon R9 M395X 4096 MB

    I usually have a number of apps running concurrently with AI: Chrome (with the following extensions: AdBlock, Amazon Assistant, Application Launcher, Boomerang, Calendly, Cisco Webex, Dropbox, Ebates, Google Docs Offline, Google Keep, GoToMeeting, GoToMeeting Pro Screensharing, Grammarly, Honey, Pinterest, Reader View, Save to Facebook, Search by Image, Soapbox, Fireshot, Wikibuy, Zoom Scheduler), Snagit, Harvest, Republic Anywhere, and occasionally Camtasia, Word, Excel, Powerpoint, Pages, Numbers, Keynote, Firefox, and/or Safari.

    I also have 2 peripheral monitors. (Incidentally, I've noticed that when I start AI, the startup screen loads on a side monitor while the rest of the app loads on my main screen--I don't know if there could be anything with AI trying to handle multiple screens.)

    When I used 23.0, I would get the "Cannot finish previewing" error about every hour while working in AI. If I didn't quit soon thereafter, AI would crash. Thankfully, the auto-save worked the few times when I didn't save in time. It seemed that if I consistently saved the document, it would take longer between preview errors, but I couldn't say for sure.

    23.0.1 seems to be working fine, but I haven't really had a need to push it much yet.

    An error occurred while saving the comment
    Casey Truelove commented  · 

    @Anonymous
    You misread me. I didn't state that the bug was our fault. My point was that anyone who CONTINUES to be hampered by the bug is at fault for not taking advantage of the available fixes.

    If I owned a store and the power went out, so I started losing customers, and I called the electric company and they told me that the electricity was still getting to my building fine and that I should go and check my breakers, but instead of going and flipping the breakers, I instead took the time to write seething comments about the electric company on their website (using my phone because I don't have electricity), I would be a fool.

    I also never said that 374 was the total number of users experiencing this issue. I chose my words carefully, mentioning that there were "only 374 votes" among the many Illustrator users. My point was that If this issue was universal, there would be many more votes. Clearly, as you admitted, it is only a segment of the users who are experiencing the issue. And my overall point was that it just so happens that none of Adobe's testers has the same configurations needed to trigger the defect. This kind of thing happens in every workplace--unforeseen complications arise--and no one is benefitted by hateful comments about it. Let's stick to CONSTRUCTIVE criticism and adding information that will actually help Adobe fix this problem.

    As for me, so far 23.01 is working fine on my Mac--but I haven't had the need to really push it yet. I was having the Preview issue every hour or so, but I could get by simply by saving often and restarting Illustrator whenever the Preview error came up. I understand that others have had it much worse.

    An error occurred while saving the comment
    Casey Truelove commented  · 

    With only 374 votes among the thousands (millions?) of Illustrator users throughout the world, this is obviously only affecting certain people. The question begged is "what is the cause?" I beta test a web-based software platform and recently some of our team caught a certain defect, but our development team couldn't reproduce it (hence why it wasn't caught before releasing to testers). It wasn't until someone was in a video chat with the dev team that one of the developers saw the Grammarly icon in the text box and asked what it was. After further review, it turned out that Chrome extensions were affecting the way the software was saving/displaying text in a certain location. Something like that is likely also true here. Since none of Adobe's testers caught the bug before release and only certain users are responding with it, it's likely that there is a problem with Illustrator interacting with something else that only certain users are using (and it just so happens that none of Adobe's testers had that combination--hence why the defect made it into the release). Short of asking everyone on this thread every other app/extension/etc. that is running on their computers while they use Illustrator, their dev team probably has to frantically check all kinds of combinations that might be causing this issue. Hopefully, they'll figure it out soon. In the meantime, they've given us two viable workarounds: roll back to 22 or try 23.01 beta. None of us should be "losing money"--we have fixes available. The only reason you should still have the issue is if you haven't done the fix--that's on you, not them. None of us should be expecting "reimbursement." I understand that you're angry, but let's try to think about it from their perspective instead of just dumping hate onto this feed. It isn't helping anyone.

    Casey Truelove supported this idea  · 

Feedback and Knowledge Base

(thinking…)