|
|
Created:
7 years, 8 months ago by Cris Neckar Modified:
7 years, 8 months ago Reviewers:
noelallen_use_chromium, cpu_(ooo_6.6-7.5), viettrungluu, dmichael (off chromium), raymes, Robert Sesek, brettw, noelallen1 CC:
chromium-reviews, piman+watch_chromium.org, raymes+watch_chromium.org, yusukes+watch_chromium.org, yzshen+watch_chromium.org, ihf+watch_chromium.org Base URL:
svn://chrome-svn/chrome/trunk/src/ Visibility:
Public. |
DescriptionAdd interface to set the sub resource crash key from Flash
BUG=N/A
TEST=N/A
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=195188
Patch Set 1 #
Total comments: 4
Patch Set 2 : #Patch Set 3 : #Patch Set 4 : #Patch Set 5 : #Patch Set 6 : #
Messages
Total messages: 25 (0 generated)
https://codereview.chromium.org/14311004/diff/1/ppapi/api/private/ppb_flash.idl File ppapi/api/private/ppb_flash.idl (right): https://codereview.chromium.org/14311004/diff/1/ppapi/api/private/ppb_flash.i... ppapi/api/private/ppb_flash.idl:109: * Specifies the URL of the current flash file. maybe "swf" instead of "file"? https://codereview.chromium.org/14311004/diff/1/ppapi/proxy/flash_resource.cc File ppapi/proxy/flash_resource.cc (right): https://codereview.chromium.org/14311004/diff/1/ppapi/proxy/flash_resource.cc... ppapi/proxy/flash_resource.cc:92: PluginGlobals::Get()->SetActiveURL(url_string_var->value()); Maybe change this one to the same code as the one below and remove the now-unneeded plumbing? I don't think it's too hard, but if you really don't want to, please add a TODO.
Well that got nice and big :) We are going to want to have the trybots have their way with this one.
https://codereview.chromium.org/14311004/diff/1/ppapi/api/private/ppb_flash.idl File ppapi/api/private/ppb_flash.idl (right): https://codereview.chromium.org/14311004/diff/1/ppapi/api/private/ppb_flash.i... ppapi/api/private/ppb_flash.idl:109: * Specifies the URL of the current flash file. On 2013/04/16 23:31:54, raymes1 wrote: > maybe "swf" instead of "file"? Done. https://codereview.chromium.org/14311004/diff/1/ppapi/proxy/flash_resource.cc File ppapi/proxy/flash_resource.cc (right): https://codereview.chromium.org/14311004/diff/1/ppapi/proxy/flash_resource.cc... ppapi/proxy/flash_resource.cc:92: PluginGlobals::Get()->SetActiveURL(url_string_var->value()); On 2013/04/16 23:31:54, raymes1 wrote: > Maybe change this one to the same code as the one below and remove the > now-unneeded plumbing? I don't think it's too hard, but if you really don't want > to, please add a TODO. Done.
+cpu@ for sanity check to make sure we aren't going to break all the things by switching the way the base url is reported. +brettw@ for owners lgtm on all the things we have to touch to accomplish this.
+rsesek to comment on whether the using the "url" key with the new scheme will map correctly with the chunking in the old scheme. Oh you did more than I expected here! :P In our conversation I was actually only referring to the plumbing related to the pepper SetActiveURL i.e. the changes you have in: content/ppapi_plugin/ppapi_thread.h content/ppapi_plugin/ppapi_thread.cc ppapi/proxy/plugin_globals.h ppapi/proxy/plugin_globals.cc ppapi/proxy/plugin_main_nacl.cc ppapi/proxy/plugin_proxy_delegate.h ppapi/proxy/ppapi_proxy_test.h ppapi/proxy/ppapi_proxy_test.cc If you want to go ahead and change all these other instances, I think that is good as well but I'm not convinced that trybot testing has good enough coverage of this stuff. I think we would need to do some manual testing to ensure that urls still end up in crash reports.
Ah gotcha. Let me submit a new patch with just those changes. Lets make sure they will map correctly and if not we can leave in the calls to SetActiveURL() in and still add the "url" crash key. then I can work on migrating the crash backend over to accept the new version while we include both and eventually get rid of the SetActiveURL() method.
This is nice! But as raymes suggests, you should definitely test this all manually. The test coverage here is very sparse. Unfortunately, this will break reporting on Linux since that doesn't have the connection to the new crash logging system. I'm working on that this week, though.
Cool, I'll save this patch for later and we can just do the basic change for now. Let me know once it works for linux. rsesek it wasn't clear to me whether this would just work or not (seems like it might). Will we need to change the crash backend to know the field name for url crash key or does it overlap the old name? if we need to change backend we can do this staged. Initially just add the crash key, change the backend once it has shipped to stable, then remove the SetActiveURL stuff after the backend is updated.
thanks! lgtm
lgtm
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/cdn@chromium.org/14311004/22002
Presubmit check for 14311004-22002 failed and returned exit status 1. INFO:root:Found 3 file(s). Running presubmit commit checks ... Running /b/commit-queue/workdir/chromium/PRESUBMIT.py Running /b/commit-queue/workdir/chromium/ppapi/PRESUBMIT.py ** Presubmit ERRORS ** Missing LGTM from an OWNER for these files: ppapi/api/private/ppb_flash.idl ppapi/proxy/flash_resource.cc ppapi/c/private/ppb_flash.h PPAPI IDL Diff detected: Run the generator. *************** --- OLD ../c/private/ppb_flash.h +++ NEW ../c/private/ppb_flash.h @@ -5,3 +5,3 @@ -/* From private/ppb_flash.idl modified Thu Mar 28 10:30:53 2013. */ +/* From private/ppb_flash.idl modified Thu Apr 18 13:09:00 2013. */ @@ -122,3 +122,3 @@ /** - * Specifies the URL of the current flash file. + * Specifies the URL of the current swf. */ Error C Header : Failed to generate range 0 : 20. *************** Presubmit checks took 2.0s to calculate.
+noelallen, owners review for ppapi/api +viettrungluu, owners review for ppapi/proxy and ppapi/
lgtm
+dmichael for owners review
Is it okay that we're not updating the version here? Does Flash need to know whether this new enum value is valid, given that it might be pushed out to a version of Chrome that doesn't support it?
I designed the function with this in mind - I don't think there is any issue. A new version of flash with an old chrome will try to pass the new enum value, which will not be caught by the switch statement in flash_resource.cc, PP_FALSE will be returned and nothing will happen. Old versions of flash with new chrome won't pass the value. So we should be good? On Thu, Apr 18, 2013 at 1:54 PM, <dmichael@chromium.org> wrote: > Is it okay that we're not updating the version here? Does Flash need to know > whether this new enum value is valid, given that it might be pushed out to a > version of Chrome that doesn't support it? > > https://codereview.chromium.org/14311004/
lgtm
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/cdn@chromium.org/14311004/22002
Presubmit check for 14311004-22002 failed and returned exit status 1. INFO:root:Found 3 file(s). Running presubmit commit checks ... Running /b/commit-queue/workdir/chromium/PRESUBMIT.py Running /b/commit-queue/workdir/chromium/ppapi/PRESUBMIT.py ** Presubmit ERRORS ** PPAPI IDL Diff detected: Run the generator. *************** --- OLD ../c/private/ppb_flash.h +++ NEW ../c/private/ppb_flash.h @@ -5,3 +5,3 @@ -/* From private/ppb_flash.idl modified Thu Mar 28 10:30:53 2013. */ +/* From private/ppb_flash.idl modified Thu Apr 18 14:46:47 2013. */ @@ -122,3 +122,3 @@ /** - * Specifies the URL of the current flash file. + * Specifies the URL of the current swf. */ Error C Header : Failed to generate range 0 : 20. *************** Presubmit checks took 2.2s to calculate.
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/cdn@chromium.org/14311004/46001
Presubmit check for 14311004-46001 failed and returned exit status 1. INFO:root:Found 3 file(s). Running presubmit commit checks ... Running /b/commit-queue/workdir/chromium/PRESUBMIT.py Running /b/commit-queue/workdir/chromium/ppapi/PRESUBMIT.py ** Presubmit ERRORS ** PPAPI IDL Diff detected: Run the generator. *************** --- OLD ../c/private/ppb_flash.h +++ NEW ../c/private/ppb_flash.h @@ -5,3 +5,3 @@ -/* From private/ppb_flash.idl modified Thu Mar 28 10:30:53 2013. */ +/* From private/ppb_flash.idl modified Thu Apr 18 15:00:17 2013. */ @@ -121,3 +121,2 @@ PP_FLASHCRASHKEY_URL = 1, - /** Error C Header : Failed to generate range 0 : 20. *************** Presubmit checks took 2.6s to calculate. Was the presubmit check useful? Please send feedback & hate mail to maruel@chromium.org!
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/cdn@chromium.org/14311004/7014
Message was sent while issue was closed.
Change committed as 195188 |