cloudtrends / chromiumembedded

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

GetDataResource doesn't load resource for IDR_TICKMARK_DASH, results in crash #111

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Use a debug version of a CEF client to search for a string.
2. Decrease the size of the client window so that a vertical scrollbar appears.
3. ScrollBarThemeChromium::paintTickmarks will crash on an ASSERT_NOT_REACHED 
when it tries to load the "tickmarkDash" resource (for showing tickmarks in the 
vertical scrollbar).

What is the expected output? What do you see instead?

Tickmarks should display in the vertical scrollbar wherever text matches 
occurred.  Instead, the debug build crashes on the assertion.

What version of the product are you using? On what operating system?

CEF 82 on 32-bit Windows 7.

Please provide any additional information below.

GetDataResource in browser_webkit_glue.cc should handle loading this resource, 
especially now that CEF supports find.

Original issue reported on code.google.com by emerick on 11 Aug 2010 at 2:47

GoogleCodeExporter commented 9 years ago
I think this is already fixed in revision 94. Can you test?

Original comment by magreenb...@gmail.com on 24 Aug 2010 at 3:11

GoogleCodeExporter commented 9 years ago
Specifically, I believe this was fixed in revision 88.  Please test with the 
latest trunk revision before reporting bugs.

Original comment by magreenb...@gmail.com on 24 Aug 2010 at 3:16

GoogleCodeExporter commented 9 years ago
Since there's been no further feedback I'll consider this issue fixed.

Original comment by magreenb...@gmail.com on 29 Sep 2010 at 2:16

GoogleCodeExporter commented 9 years ago
Sorry, I forgot to reply to this.  I haven't had a chance to test this (it's a 
bit difficult for me to use a new version of CEF at the moment), but your 
analysis sounds correct.  Sorry for the false report.  I did see that revision 
when initially checking the bug database, but it didn't seem relevant at the 
time, so I glossed over it.

Original comment by emerick on 29 Sep 2010 at 2:23