[proFit-list] ProFit 'cannot create this type of window' message

[ivan]

Jeremy, all that you describe might have resulted in some freak event that corrupted a saved application state (maybe). Close all the files that open up when pro Fit opens, then quit, restart, and see if you have the same problem again. If this doesn’t fix the issue,  delete the file com.quansoft.profit.savedState  from the folder  ~/Library/Containers/com.quansoft.profit/Data/Library/Saved Application State/, and try again to quit and restart. If this still doesn’t work, then please contact us directly at profit at quansoft.com!
thanks!
> On Mar 16, 2018, at 2:24 PM, Jeremy Harbinson <jeremy_harbinson at me.com> wrote:
> 
> Hi,
> This appears to be a rerun of a problem I had some time ago: I have copied my post of 4th July 2017 below - it seems to be same problem:
> 
> "All of a sudden ProFit seems unable to execute any New Data, New Function or New Drawing commands - when I try to do so I get a message:
> 
> NewWindow: can not create this type of window
> 
> which is a bit of an end to things. 
> 
> I can open old files - no problem there, but if I try to select a column in a data file, ProFit crashes. If I restart ProFit, all previously open files reopen, but Profit remains unable to create new data, function or Drawing windows. There is only one other unusual thing at the moment; Python is not working in Profit as I have recently updated the Python system. "
> 
> At that time it concerned ProFit 7.0.10, now it is with 7.0.11 (the problem was fixed with release of 7.0.11), and now my version of OSX is: 10.13.1. Interestingly enough, Python is currently not working in ProFit as I have just changed to Anaconda, but I guess this is just a coincidence. 
> 
> The problem may be connected to a hard crash of OSX occurring earlier today while ProFit was active - ProFit was working fine before that. I have attached the ProFit crash report below
> 
> all the best,
> Jeremy Harbinson
> 
> 
> 
> Process:               pro Fit NAS [52610]
> Path:                  /Applications/pro Fit 7.app/Contents/MacOS/pro Fit NAS
> Identifier:            com.quansoft.profit
> Version:               7.0.11 (5202)
> Code Type:             X86-64 (Native)
> Parent Process:        ??? [1]
> Responsible:           pro Fit NAS [52610]
> User ID:               503
> 
> Date/Time:             2018-03-16 19:07:52.096 +0100
> OS Version:            Mac OS X 10.13.1 (17B1003)
> Report Version:        12
> Anonymous UUID:        9AEB8A61-C7AB-4676-5EB7-6FE2CFD1A41B
> 
> Sleep/Wake UUID:       764A56CA-8B48-4B66-BC4E-D6DA96F0EF73
> 
> Time Awake Since Boot: 28000 seconds
> Time Since Wake:       75 seconds
> 
> System Integrity Protection: enabled
> 
> Crashed Thread:        0  Dispatch queue: com.apple.main-thread
> 
> Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
> Exception Note:        EXC_CORPSE_NOTIFY
> 
> Termination Signal:    Segmentation fault: 11
> Termination Reason:    Namespace SIGNAL, Code 0xb
> Terminating Process:   exc handler [0]
> 
> VM Regions Near 0:
> --> 
>     __TEXT                 00000001083ce000-0000000108736000 [ 3488K] r-x/rwx SM=COW  /Applications/pro Fit 7.app/Contents/MacOS/pro Fit NAS
> 
> _______________________________________________
> proFit-list mailing list
> proFit-list at quantum-soft.com
> http://quantum-soft.com/mailman/listinfo/profit-list_quantum-soft.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://quantum-soft.com/pipermail/profit-list_quantum-soft.com/attachments/20180318/dfec9049/attachment-0001.html>