Repeated browser crash

Ive created a dmp file after restarting the browser half a dozen times this evening

Each time I was playing music from you tube. but this has never been an issue before

Updated to the latest version yesterday

Running Win 7 & comodo dragon 17.1

Same here, with the new update browser keeps on crashing and asking to relaunch, does not seem to be an issue with any specific website through,will check to find out after disabling addons,if it works,but at the moment,crashes quite often.

If you have Under The Hood> Do not allow websites to know where you came from (suppress HTTP Referrer header) enabled/ticked, please try is disabled/not ticked.

Try disabling all plugins and see if that fixes it for you.

When the problem is plug in related disable VLC plugin. Opera browser recently disabled the use of VLC plugin because it is too unstable; it crashes too much.

hy,repeated browser crash
Application Name: dragon.exe
Application Version:
Application Timestamp: 4f1eaa58
Fault Module Name: dragon.dll
Fault Module Version:
Fault Module Timestamp: 4f1ea9a9
Exception Code: 80000003
Exception Offset: 007886f0

this isnt a plugin problem,so how can i turn back to previous version?

Happening here as well with the latest version. it happens most when i close a YouTube tab that has played video.

same here… every time crash

If you are experiencing crashes please submit them as bug in Bug Reports - CD following How to Submit Bug Reports (read this if you want them fixed).

Also see if disabling plugins, in particular VLC plugin, makes the problem go away or not and add that to your bug reports. That will greatly help Comodo.

Exactly the same here. I dont have vlc plugins installed. I have recently started a thread regarding the issue (and to avoid crashing – at least most of the time – you should go to about:plugins to enable pepperflash before you visit YouTube. Pepperflash is always automatically disabled when you close CD). Unfortunately I havent yet got any response from the CD team on that thread. I think this might be a bug with Chromium 17?