Loading Profile...
Firefox and Safari browsers...unexpectedly quit in OS X
When working on an M7 draft version script, I'm having repeated 'unexpected quits' of multiple browsers in Mac OS X.
I'm currently switching back and forth between the beta version of Safari 4.0.2 and Firefox 3.5
Experiencing multiple quits for both browsers.
No other tabs or browser windows are open and no typing or other activities are occurring during the quits.
Repeatedly, I'm switching to FCP to perform edits while flipping back to view the script in draft mode. All of a sudden, without scrolling, typing or otherwise manipulating the browser in any way, the browsers just shut down.
My uneducated guess might be that the auto-save function or other background process is causing the problem...?
I'm currently switching back and forth between the beta version of Safari 4.0.2 and Firefox 3.5
Experiencing multiple quits for both browsers.
No other tabs or browser windows are open and no typing or other activities are occurring during the quits.
Repeatedly, I'm switching to FCP to perform edits while flipping back to view the script in draft mode. All of a sudden, without scrolling, typing or otherwise manipulating the browser in any way, the browsers just shut down.
My uneducated guess might be that the auto-save function or other background process is causing the problem...?
I’m having to restart and log in repeatedly
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
-
Inappropriate?Brent,
that's disconcerting. Can you invite support@market7.com to the project so we can try to recreate locally? -
Inappropriate?Not sure if this screen shot will be helpful to troubleshooting but here is an error message that Firefox give upon restart stating it's inability to automatically reinstate the session and windows...
-
Inappropriate?Don't want to send you guys on a wild goose chase if the problem is indeed on my end and associated with my machine only. Trying to verify the same issue on another machine but have different versions of the two browsers.
Here is the latest error message from Safari after an unexpected quit ( I wasn't even at the machine when it quit). Came back from lunch to this message:
-
Inappropriate?Brent,
Definitely a Final Cut Pro library conflict issue. Are there any plug-ins for FCP that you loaded recently? The key is isolating which FCP is conflicting our Script Editor so we can develop a solution. -
Inappropriate?I don't use any plug-ins for FCP at all that I'm aware of. I'll look and see if there's something I installed a long time ago, but this particular machine is a production box that we keep pretty stock as a dependable workhorse.
We are in the middle of production and I don't normally update FCP to the latest version when mid-project. Can't risk having FCP quit issues while under the gun to complete a client project.
Perhaps one of my other machines can be used to experiment further...
I'll try to set up the same environment on another 8-core Mac Pro we have.
It has older versions of the browsers however and I don't think that Firefox 3.x and Safari 3.x where having issues as described.
I'll post back... -
Inappropriate?Tests were completed on a separate machine with interesting results.
First attempt was to open up Safari and Firefox first and load the scripts in each. Then an attempt was made to open up FCP on that machine...no go. Final Cut Pro just hung on the load screen and locked up the entire machine.
Restarted machine and opened Final Cut Pro first on second attempt. Opened fine.
Then opened Safari and loaded a script in 'Draft' mode.
Opened Firefox next and loaded same script in 'Recent Published'.
Hid all applications and worked in other programs.
Within a half hour, Safari in Draft mode quit and Firefox in Publish mode remained open.
Switched the scenario with the exact opposite findings. Firefox quit while in Draft mode and Safari remained open displaying the Published version.
These tests verify the same behavior as the previous versions listed for Safari and Firefox in the first few threads.
These tests were with:
Safari 3.2.3
Firefox 3.0.1
Final Cut Pro 6.0.5
Quicktime 7.6.2 -
Inappropriate?OK Brent, We owe you an answer but this is not a simple problem. We know it is probably very frustrating for you. We are not as fluent in the Final Cut Pro library so there is some experimentation we need to do to try and isolate and put this bug to rest. Do your best to work around this (by not working in 'edit' mode while FCP is open and we'll get a fix for this ASAP.
I am trying to recreate it locally, once we can reliably do that, we'll work with the Apple FCP developers toward a solution. I expect this will be a 3-4 week solution but I am crossing my fingers for something faster.
Shannon -
Inappropriate?For me, this issue isn't a big problem, just more of a nuisance.
I'm not in writing mode. Currently, when the script is in draft mode, I'm just making minor changes here and there.
I must say that from the beginning, your team has kept such high priority against never loosing data that I haven't lost any major changes at all because of the M7 server-side 'auto-save' feature.
Stressing the auto-save factor from the beginning of the Market 7 development has really provided peace of mind, even when these minor bugs pop-up.
All thanks to your team for designing a robust data storage method. Without it these bugs would feel more damaging, but so far, I don't feel the bug has caused me to feel as if any data was ever at risk.
Let me know if I can provide any other troubleshooting from my side.
EMPLOYEE
