JDISALVO
-
Posts
9 -
Joined
-
Last visited
Posts posted by JDISALVO
-
-
Update: I realized I may have incorrectly characterized what's happening as a "crash," when in fact what is happening is a fatal freeze that requires a me to force quit the application (either via Task Manager "end task" or the dialog that inquires if you want to force quit or wait for the application to respond)
I mention this because I experienced another one of these fatal freezes this afternoon that lost maybe 30 minutes of work. I immediately opened the folder where I would expect to find a crash report but the folder is empty. Wondering if this opens up other possible fixes?
-
I'm laying out a document using scans of hand drawings and recomposing them on the page with picture frames.
I like to reduce file sizes using Bluebeam Revu PDF reader before sending them via email. When I use Revu's "reduce file size" function, which crops all PDF content to its frames, I get two different results depending on the source image file format.
JPG source files before and after file size reduction:
PDF source files after file size reduction:
Any ideas what's going on here? Apologies if this isn't a bug and simply user error.
-
20 hours ago, RichardMH said:
If you haven't already, try turning off hardware acceleration. Edit->Preferences->Performance.
I assume your graphics drivers are up to date.
Posting crash reports will help them sort it out.
Thanks for this suggestion! Hardware acceleration is turned off already (part of my own troubleshooting routine), and drivers are all up to date.
I will begin to save and post crash logs when this occurs (still going on but less frequent this week).
-
2 hours ago, Hilltop said:
Indeed, you mentioned rebooting. So sorry, I hadn't read your post carefully enough. Hope you get the issue sorted!
No worries, thank you for the response regardless.
Still interested to hear if others have experienced this and whether they've found a workaround.
-
7 hours ago, Hilltop said:
Try rebooting your system.
As stated in the original post, Publisher will only reopen after rebooting the entire computer, which I have been forced to do close to 20 times in the past week. Am I misunderstanding - is there something else to be rebooted?
-
Wanted to update that I reproduced the exact same crash after a weekend away from work with the computer shut down.
This morning my file froze while I was on a video call with colleagues panning around the document to demonstrate my progress. After forcing a quit, I can't seem to reopen Publisher. The software goes through the process of loading fonts and other settings before hanging on this screen:
-
Not sure exactly is causing the frequent crashing (seems to have many possible sources), but after a crash I'm unable to reopen Publisher 2.0 on Windows 10 without rebooting my workstation. Is this an issue anyone else has experienced? Is there any workaround?

Cannot reopen Publisher 2.0 after crash
in V2 Bugs found on Windows
Posted
I have to plead ignorance on this one - I'm not sure how much would be considered lots.
This is what my device specs look like: