rakasza wrote:I have a strange problem since yesterday. I have old desing google search [with black bar at the top]. I cleaned everything and reinstall SRW... help
AVN6293 wrote:Long time lurker here!
Just wanted to say this has got to be one of the buggiest versions yet!
AVN6293 wrote:Iron is constantly crashing for me
Problem Event Name: APPCRASH
Application Name: chrome.exe
Application Version: 34.0.1847.116
Application Timestamp: 535a70bc
Fault Module Name: chrome.dll
Fault Module Version: 34.0.1847.116
Fault Module Timestamp: 535a7066
Exception Code: 80000003
Exception Offset: 0053e640
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1031
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Is there some place where I can re-download version 33, please?
dph3055 wrote:Just as an observation:
I have used Iron for more than a year. I appreciate the efforts that have gone into to providing a browser devoid of the all the "phone home" activities found in the regular version of Chrome.
The last few Iron releases have been buggy at best or just down right broken at worst. Either the Chrome source code is no longer conducive to porting into Iron or the developers have decided to focus their attentions elsewhere.
I for one am still running a v30 release as every time I attempt to install a newer version, I lose stability and functionality within Iron. I am getting to the point that I just don't install new releases anymore and I am sure I am not the only one. This is a growing problem for the developers and for Iron itself. The long term future of a browser that people are reluctant to upgrade speaks volumes towards to the future longevity of this project.
I would ask the developers to either recommit to Iron and begin to seriously test new releases before the are let loose on the masses or decide that Iron is no longer worth their time and let us know. To continue as we have been with release after release causing more problems than it addresses is nothing less than death by a 1000 cuts. It would be in everyone's best interests to have one final well tested release of Iron and then shelve the project if the time and effort going forward is too much for the developers to commit to.
bugman wrote:I have not choice but to agree with this. Iron versions from 27~30 where just starting to become stable but now the browser has random crashes and broken features so much so i can no longer consider it a daily rider.
I don't blame the iron developers its probably more a issue with the upstream trunk and branch teams at google doing what they can to try and continue to force us into their eco system by sabotaging the chromium source code.
Its now above all times that we need to remain ever so vigilant and come up with innovative solutions to give them the finger.
Users browsing this forum: Bing [Bot], Google Adsense [Bot] and 12 guests