Version 7.2.2 crashes a lot
I reverted back to the previous version. 7.2.2 brings back that bug where if I am deleting files it crashes randomly, and I loose everything that was done in that session. So I think I will stay with the previous version unless I upgrade to a new camera which is not out yet, or a must have feature is added. I sent the crash dump to Phase One when the window popped up. I don't know if they look at those dumps or not. Running Windows 8.1 64 bit. I don't need anything in the update so I will not file a support case, too busy this time of year!
0
-
[quote="NN8899721" wrote:
I...
I sent the crash dump to Phase One when the window popped up. I don't know if they look at those dumps or not.
Yes, they do look at the crash dumps.0 -
[quote="NN8899721" wrote:
I reverted back to the previous version. 7.2.2 brings back that bug where if I am deleting files it crashes randomly, and I loose everything that was done in that session. So I think I will stay with the previous version unless I upgrade to a new camera which is not out yet, or a must have feature is added. I sent the crash dump to Phase One when the window popped up. I don't know if they look at those dumps or not. Running Windows 8.1 64 bit. I don't need anything in the update so I will not file a support case, too busy this time of year!
I can sympathise with your point of view if you are very busy.
On the other hand a generic crash dump may not help you identify a potential problem with, say, your session files (Do you get the problems with a completely new session as well as existing sessions?) or something that might quite specific to your system and perhaps the systems a few other people are running. I mention this since many people seem to be running very happily with versions that others are finding to be problematic.
Reverting keeps you running for now but there is just that possibility that you have some sort of deeply hidden glitch in your system somewhere - perhaps data issues that you cannot readily see - and that they will appear unexpectedly anyway at an inconveniently busy time in what you feel comfortable is a working version. I mention this because the only similar problem I have had with V7 Capture One caused a session to crash, apparently randomly and irregularly. By chance I noticed a bad preview file (just after I had decided it was time to create a support case) that I could not get to process correctly. I deleted the edits for the file and created a new edit and that fixed all of the problems I was having with the session.
So my conclusion was that for some unidentified reason the edit file had become corrupted and was adversely affecting the session database file processing causing hanging and crashing somehow. I guess you write some code to deal with that as a "fix" but without a source problem how would you know to do it and where to start? Would it be a sensible use of resources?
On the other hand the opportunity to analyse the problem might help the support team to identify such data disruption problems more quickly and put them in a position to respond very quickly with advice that would help to identify and eliminate such problems. You and I may see such things once in ten years and so never gain the sort of experience to now where to look when under pressure (or at least we would hope never to have that amount of experience!) but supporting a large user base the Phase team might see such problems more often and so be able to respond more quickly and more accurately to resolve the problems.
I don't think is is possible to avoid things like rare file glitches. I have seen such things in a small number of very different systems over the years. Centralised support operations are more likely to be exposed to such events and keep records of what to do and how to resolve the problems. But only if they are told about them.
Over time they may also develop tools that help to check and correct errors or, possibly, spot weaknesses in the depths of the system design and find ways to make then stronger - perhaps adopt new development tools for example as they available. To know that such decisions may be required demands feedback from users.
Going back to my problem from last year, once I had made the connection to the problem edit file and deleted it from the session it did not take me long to prove to my satisfaction that the problem was resolved - which was a huge relief with a lot of files to process. I have not seen the problem again.
It would have been nice to identify the specific cause ... but in fact that may not be important since it seems to have been a random problem. On the other hand knowing generically where a problem may arise can be extremely important for saving time at some point in a process when thing don't seem to be working quite as well as expected.
I could provide examples of similar problems from working with other, non-photograpic, applications but that would be going a long way off topic and is probably not pertinent here except to observe that not all problems can be foreseen and some may not be correctable by software changes at the point of use - at least not logically. However a support group that has been allowed to become well informed can be of enormous assistance with unpredictable problems when their customers are working under pressure and need help.
HTH.
Grant0
Post is closed for comments.
Comments
2 comments