pacificIT / chromiumembedded

Automatically exported from code.google.com/p/chromiumembedded
0 stars 1 forks source link

[CEF3] Crashing inside prerenderer client #608

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Reproduce problem, using CEF3/651:
1. Open CEF3's cefclient.
2. Enter URL: http://www.google.com.ua/#hl=uk&q=html5test (it will be 
redirected in more coplex 
(http://www.google.com.ua/#hl=uk&q=html5test&fp=1&bav=on.2,or.r_gc.r_pw.r_qf.,cf
.osb&cad=b).
3. Wait 2-10 secs - and you will got crash (in both debug and release versions).

Of course this pages opened normally in Chrome (21.0.1145.0 dev-m).

Sorry, can't obtain textual callstack (it is not writes in any file?), so see 
attached screenshot. Selected line with assert fails.

Original issue reported on code.google.com by fdd...@gmail.com on 28 May 2012 at 11:00

Attachments:

GoogleCodeExporter commented 9 years ago
In addition to this issue - it will be cool have option to enabling/disabling 
prerender.

Original comment by fdd...@gmail.com on 28 May 2012 at 11:09

GoogleCodeExporter commented 9 years ago
I never thought about the fact that Chromium now does pre-rendering which is 
something we would not want it to do in our line of business app. We would not 
want any transactions to be run against our core system unnecessarily from a 
linked page.

Original comment by custa1...@gmail.com on 29 May 2012 at 12:29

GoogleCodeExporter commented 9 years ago
Oh yes, you are right - prerendering is triggered by <link rel="prerender"> 
elements manually.

Original comment by fdd...@gmail.com on 29 May 2012 at 11:09

GoogleCodeExporter commented 9 years ago
UPDATE: To test prerendering is better to use 
http://prerender-test.appspot.com/ . Currently loading of this url cause crash 
in cefclient.

Original comment by fdd...@gmail.com on 29 May 2012 at 11:15

GoogleCodeExporter commented 9 years ago
Revision 652 fixes the crash by adding stub implementations for 
WebKit::WebPrerenderingSupport and WebKit::WebPrerendererClient. Chromium's 
prerendering implementation currently lives in chrome/renderer/prerender and 
chrome/browser/prerender. I'm not aware of any plans currently for add 
prerendering support to the Content API.

Original comment by magreenb...@gmail.com on 29 May 2012 at 5:24

GoogleCodeExporter commented 9 years ago
Great, thanks!
PS: I think that stub it is enough. At least at this moment.

Original comment by fdd...@gmail.com on 29 May 2012 at 7:38

GoogleCodeExporter commented 9 years ago
Same problem with CEF1 trunk fixed in revision 657.

Original comment by magreenb...@gmail.com on 30 May 2012 at 8:36