fxDreema Connector stops working in Google Chrome
-
From time to time I find I have to remove and re-install fxDreema Connector in Google Chrome.
After a period of use (no specific length of time) clicking on either of the "build as" options neither produces a "file written to..." message nor does the Metatrader/Metaeditor button work that appears after the build process.
-
What if you reload only the page, not the plugin?
-
I'll try that next time this occurs and let you know.
Many thanks. -
After around 4 hours of the web fxdreema being loaded, I noted that the fxDreema Connector icon which normally appears beside the "bookmark this page" star in Google Chrome had disappeared. In this state clicking one of the "build as" links results in a "building" message, followed by the appearance of the button to click for Metatrader or Metaeditor, but no "saved to..." message. The buttons to Metatrader or Meateditor do nothing when clicked.
So I pressed F5 to refresh the page in the browser and the fxDreema Connector icon re-appeared. However, clicking the "build as" links results in the same sequence, ie., a "building" message, followed by the appearance of the button to click for Metatrader or Metaeditor, but no "saved to..." message, and the buttons to Metatrader or Meateditor do nothing when clicked.
So this time I closed the browser, and re-launched it. After launching the web generator the fxDreema Connector icon appeared as normal. But again, clicking the "build as" links results in the same sequence, ie., a "building" message, followed by the appearance of the button to click for Metatrader or Metaeditor, but no "saved to..." message, and the buttons to Metatrader or Meateditor do nothing when clicked.
I then opened chrome://extensions, and drag-dropped the fxdreema-connector-0.2.crx into the extensions page, as per Google's instructions for adding extensions to Chrome from sources outside their Chrome Web Store. I closed the chrome://extensions page.
However, as before, clicking the "build as" links results in the same sequence, ie., a "building" message, followed by the appearance of the button to click for Metatrader or Metaeditor, but no "saved to..." message, and the buttons to Metatrader or Meateditor do nothing when clicked.
I opened chrome://extensions again and removed the fxDreema Connector. Thereater I drag-dropped the fxdreema-connector-0.2.crx into the extensions page again to re-install it. But still clicking the "build as" links resulted in the same sequence, ie., a "building" message, followed by the appearance of the button to click for Metatrader or Metaeditor, but no "saved to..." message, and the buttons to Metatrader or Meateditor did nothing when clicked.
I closed and re-started Chrome. Still the same problem.
I removed fxdreema-connector-0.2, and re-installed fxdreema-connector-0.1. This time clicking the "build as" links worked as expected.
I uninstalled connector 0.1 and reinstalled 0.2. The fault returned. So I went back to 0.1, and the fault had gone again.
Hope this helps you!

Thanks again.
James.
-
exact same procedures and results for me!

-
Good explanation of the problem, really thank you

If 0.1 works well, work with it. The difference between both versions is the size of the .dll file inside, which is smaller in 0.2 version because I've made some changes in Visual C++ environment... but I'm not really sure what changes

Well, I think I have to wait for that problem to start happening here. Meanwhile, what is your free RAM normally? On both of you

-
I'm running with 4 Gb of RAM. Don't know off hand what the free memory is, but am only running 1 tab of Google Chrome with the generator and MT4. Should therefore have loads of free memory.
I also am finding that Chrome is auto-updating to v 0.2 of the extension, which means I have to manually downgrade each time I launch.
-
Oh yes, the power of automatiozation

So, basically, 0.2 no longer works on your PC? Is it possible that I can investigate it on your PC... if you don't have what to do?
-
1.5 GB free memory.
I'll get back to you regarding access to my PC. Not sure if I'm permitted to allow it!