If you look at my post history, you will easily find that I am a fervent supporter of DOpus, so hopefully no one will interpret this as an attempt at slander or anything of the like.
Since this this latest round of beta (and YES I understand what I just wrote - This is BETA software, ergo prone to crashes) I have been experiencing 1 - 2 crashes per day. I wouldn't consider myself a power user by any means, but this is completely unlike my expereince with DOpus 12. I think in the years I was using v12, I had .... 1 crash - TOTAL? and It was probably my fault for doing something dumb. With v13 and these weekly beta releases, I am just doing normal tasks and the window will freeze, I attempt to close it, won't close, hit the button again, then get the "Restart/Close/etc" options that get the program to close or restart. I have had several crashes when I was using the Viewer Window, so I am thinking it might be codec related, or something else entirely. I'm not a programmer. Today just cooked my noodle because I was literally doing nothing, restore the opus window, and it almost instantly froze on me. This is very not normal for the software, and is why I am making this post. I am hesitant to share crash logs as I am unaware of what information is contained within the log itself and can't afford to have my information out in the wind (not that I don't trust GPS, I just can't afford another attack on my identity, I'm just getting over one now from last year at tax time. Just curious if others are having similar issues or not.
Crashes are often caused by something else on the system (since lots of shell extensions run inside out process), but may also be a bug in Opus itself. Only the logs will reveal that kind of detail.
screw it I'll send them. I only see two logs but I have had at least 4 crashes in the past week, so don't know what up with that. I'll submit them through the crash submit thing in the prog. Thanks Leo
Chances are they already know your name, email, and payment info
The crash ID is probably a bit over 300. That's the total number of Opus 13 mini-crashes after almost a year of beta testing and normal usage. So you seem to get more than your fair share.
I have had several crashes (small and big) in the past year but very few since Opus 13 was released.
I guess I have been callous in my life's experience with beta releases in general, and never had that much trouble with them so I have been kind of lax in adopting them. I think I am going to start abstaining in going for the ultra-new releases and just stick with the tried and true.
you're a 100% right about already having my info. It's been such a pain in the ass dealing with this identity crap, I swear to god. I'm just paranoid. I know it's probably explained in depth somewhere in some fine print, but one of my biggest issues was just not knowing in general what was being summitted when I would send a crash report. Maybe if there was a link to the disclaimer on the crash report screen to where it explains what is included with a crash report - that would satisfy me entirely.
The DMPs don't tell us which module the problem is in, but it's very likely to be something external to Opus.
It looks like something has created a window on the lister's thread, but then unloaded its DLL so that the code behind that window no longer exists. When any message is sent to the window, it crashes the process.
If that only started happening for you recently, are you using the new option to remove the titlebar ("Move top-row toolbars into the window title bar")? If you are, my bet is you have something installed that adds extra buttons to window titlebars, and is confused by that new option. Those are the main things I know of which create persistent windows on our threads.
(It could also be a shell extension or similar, that runs in-process and displays a UI. But those usually close their windows before they're unloaded.)
sorry for delayed response. I am not using the remove the title bar option. I tried for about 10 minutes this program called Translucent Menus and it made nearly all my program crash. It wasn't installed, just running as a portable install, but I erased that damn thing, and it seems like somehow there is something still on my system remaining from that. I'm going to dive deep and see if I can find the culprit hiding somewhere. Thank you for pointing me in the right direction.
(Just wanted to add that this was about 2 months ago, and the after effect of this program has been subtle, but I am almost certain these problems are coming from that program now.)
well i did a thorough run through of malware, old installs, portables, updated software, dism the system, system image restore, and the works and i am still getting the errors about once a day. I have had one yesterday and today.
Specifically in reponse to the "move top row toolbars" that is the ONLY option i have disabled in that menu screen. Are there any other options or configurations that could be responsible for this?
I fired up the old process explorer and found this additional OpusRT process with a crash handle on it. I took a screen shot if this makes any sense to someone else.
oh ok thanks. Could this be resolved with a uninstall/reinstall or will it persist even after that? I'm getting a little irritated with myself and starting to think of more and more drastic measures to fix this damn thing.
Probably, but not of Opus. It’s likely something else, from what the DMPs look like. Tracking down what is the hard part, but hopefully not if you focus on tools that open windows within, or add UI elements to, other software.
Thats the criteria ive been trying to use to assess what i have on my system either installed or portrable and im coming up empty. The way i am personality wise has made this to be no longer about the irritation if it crashing, but now trying to explain this damn unknown variable on my PC screwing with me. When i get this way i will evetually end up formatting the whole thing and starting over if a solution doesnt come quickly enough.
Hopefully it doesnt come to that, but either way I'll be sure to share here if i figure out whats doing it. Thank you for your help and patience @Leo