This is how iron starts up now, even after the actual relaunch. So in other words, just does not start up. Is this a feature of the portable version or of Iron itself?
I guess it should work if I delete only a file or directory but I don't want to lose my settings. Any similar experience with Iron or a solution in mind?
See picture for reference:
http://i.imgur.com/OOcYH.png
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Begin by renaming the Data directory to something else in the folder where it is installed, just to see if your profile is the problem.
Previously known as kAlug.
Good idea! The problem on D (with Iron Portable) is now solved. What still remains is the problem on C. I don't have Iron on C installed, just as it is the default browser it created a directory on C "Chromium." But even after I deleted that directory the problem still persists. Strange.
I reproduced the problem. Now a plain Iron Portable crashes on drive D. I removed the Data directory and it still crashes.
I think I got what's the problem by now. I recently started running two instances of Iron and its sessions in the background might don't play well with each other.
Is there a solution for that? Can I run two instances?
Background tasks clash with each other.
The question is the error comes from Chromium, Chrome, Iron or the Portable version of any of it? So that I can address my concern accordingly.
Quick update: Portable Chrome doesn't seem too do this.
Chrome is also crashed by using the Free Download Manager to monitor flash videos...