summaryrefslogtreecommitdiffstats
path: root/content/app
Commit message (Collapse)AuthorAgeFilesLines
* Android content shell bringup.jrg@chromium.org2012-05-101-4/+25
| | | | | | | | | | | | | | | | | | Build media java files (we weren't). Fix adb_install_content_shell for cases where the app was stuck. Add upstream staging gyp var / #define. Be more consistent about jar output files (all in lib.java). Upstream a bunch of random files (e.g. ppapi). Upstream a bunch of java and native code hit as part of shlib init. Properly package jar files in content shell. BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10377059 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136219 0039d316-1c4b-4281-b951-d872f2087c98
* Move the Linux zygote stuff into its own per-process directory.brettw@chromium.org2012-05-081-1/+3
| | | | | | | | | | | | | | | | | The zygote is really a separate process and doesn't belong in the browser subdirectory. I separated out the common constants used for communication into content/[public/]/common so the zygote code doesn't depend on browser. This leaves zygote_main_linux alone in its own directory. I'm going to be doing some more refactoring and probably adding a new file or two here. This does not yet add a new build target for the zygot process. BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10388013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@135891 0039d316-1c4b-4281-b951-d872f2087c98
* Route calls to tcmalloc MallocExtension through allocator agnostic interfacejamesr@chromium.org2012-04-281-0/+20
| | | | | | | | | | | | | | | | Our various libraries should not be picking or depending on a particular allocator choice - that should be an application level choice. This creates a generic AllocatorExtension interface that can optionally be backed by entry points to a particular allocator's MallocExtension interface if the application chooses to. BUG=125003 TEST=compiles, chrome://tcmalloc works Review URL: http://codereview.chromium.org/10239012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@134434 0039d316-1c4b-4281-b951-d872f2087c98
* Metro/HiDPI: Mark Chrome as HiDPI aware on Windowssail@chromium.org2012-04-251-0/+4
| | | | | | | | | | | With this CL Chrome is marked as HiDPI aware if the enable_hidpi build flag is set. BUG=114311 TEST=Changed Windows to 2x DPI scale. Ran Chrome. Verified that 2x icons were used. Review URL: http://codereview.chromium.org/10086009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133826 0039d316-1c4b-4281-b951-d872f2087c98
* Get chrome:// dev tool urls hooked up in content_shell.michaeln@google.com2012-04-201-0/+4
| | | | | | Review URL: https://chromiumcodereview.appspot.com/9950040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133107 0039d316-1c4b-4281-b951-d872f2087c98
* Move --user-agent overriding logic from chrome into content.scherkus@chromium.org2012-04-091-3/+12
| | | | | | | | | BUG=117259 TEST=start chrome and content_shell with and without --user-agent and visit a site like www.whatsmyuseragent.com to verify the expected user agent Review URL: https://chromiumcodereview.appspot.com/9623027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131365 0039d316-1c4b-4281-b951-d872f2087c98
* Enable audio/video tag in content_shellvrk@chromium.org2012-03-072-1/+13
| | | | | | | | | | | | | | | | Some media initialization work needed to be added to the shell in order for the ffmpeg stubs to be loaded and for the media tags to be recognized. AudioManager also needed to be added to the shell, as the Chromium-equivalent lives in BrowserProcessImpl, and the media code should not assume the MediaInternals has been created. BUG=112043,116906 TEST=content_shell builds and can play the videos in the bug above Review URL: http://codereview.chromium.org/9316077 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125442 0039d316-1c4b-4281-b951-d872f2087c98
* Do not call ContentMainDelegate::ProcessExiting if BasicStartupComplete ↵marshall@chromium.org2012-02-141-4/+12
| | | | | | | | | | | return true. This fixes a regression on Linux caused by http://crrev.com/121454. BUG=114121 TEST=Run chrome --version Review URL: http://codereview.chromium.org/9348087 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121906 0039d316-1c4b-4281-b951-d872f2087c98
* Support sharing of ContentMain and BrowserMain code with embedded use cases ↵marshall@chromium.org2012-02-103-484/+568
| | | | | | | | | | | | | | | | | | | | (try #3). For the browser use case it is convenient to have a single ContentMain entry point function that handles all initialization, run and shutdown. For embedded use cases it is often necessary to integrate with existing application message loops where initialization and shutdown must be handled separately. To support sharing of this code the following changes were required: 1. Refactor the ContentMain function to create a ContentMainRunner class containing separate initialization, run and shutdown functions. 2. Refactor the BrowserMain function and BrowserMainLoop class to create a BrowserMainRunner class containing separate initialization, run and shutdown functions. 3. Add a new BrowserMainParts::GetMainMessageLoop method. This is necessary to support creation of a custom MessageLoop implementation while sharing BrowserMainRunner initialization and shutdown code. BUG=112507 TEST=none Review URL: https://chromiumcodereview.appspot.com/9375017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121454 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 121236 - Support sharing of ContentMain and BrowserMain code with ↵marshall@chromium.org2012-02-093-570/+484
| | | | | | | | | embedded use cases (try #2). Tests failing. Review URL: https://chromiumcodereview.appspot.com/9372027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121245 0039d316-1c4b-4281-b951-d872f2087c98
* Support sharing of ContentMain and BrowserMain code with embedded use cases ↵marshall@chromium.org2012-02-093-484/+570
| | | | | | | | | | | | | | | | | | | | (try #2). For the browser use case it is convenient to have a single ContentMain entry point function that handles all initialization, run and shutdown. For embedded use cases it is often necessary to integrate with existing application message loops where initialization and shutdown must be handled separately. To support sharing of this code the following changes were required: 1. Refactor the ContentMain function to create a ContentMainRunner class containing separate initialization, run and shutdown functions. 2. Refactor the BrowserMain function and BrowserMainLoop class to create a BrowserMainRunner class containing separate initialization, run and shutdown functions. 3. Add a new BrowserMainParts::GetMainMessageLoop method. This is necessary to support creation of a custom MessageLoop implementation while sharing BrowserMainRunner initialization and shutdown code. BUG=112507 TEST=none Review URL: https://chromiumcodereview.appspot.com/9347022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121236 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Support sharing of ContentMain and BrowserMain code with embedded ↵evan@chromium.org2012-02-063-570/+484
| | | | | | | | use cases." This reverts commit r120574. Test failures. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120581 0039d316-1c4b-4281-b951-d872f2087c98
* Support sharing of ContentMain and BrowserMain code with embedded use cases.marshall@chromium.org2012-02-063-484/+570
| | | | | | | | | | | | | | | | | | For the browser use case it is convenient to have a single ContentMain entry point function that handles all initialization, run and shutdown. For embedded use cases it is often necessary to integrate with existing application message loops where initialization and shutdown must be handled separately. To support sharing of this code the following changes were required: 1. Refactor the ContentMain function to create a ContentMainRunner class containing separate initialization, run and shutdown functions. 2. Refactor the BrowserMain function and BrowserMainLoop class to create a BrowserMainRunner class containing separate initialization, run and shutdown functions. 3. Add a new BrowserMainParts::GetMainMessageLoop method. This is necessary to support creation of a custom MessageLoop implementation while sharing BrowserMainRunner initialization and shutdown code. BUG=112507 TEST=none Review URL: https://chromiumcodereview.appspot.com/9190018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120574 0039d316-1c4b-4281-b951-d872f2087c98
* android build: progress on content and libjingle.jrg@chromium.org2012-01-271-2/+4
| | | | | | | | | | BUG=None TEST= Review URL: http://codereview.chromium.org/9271028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119334 0039d316-1c4b-4281-b951-d872f2087c98
* Add a mechanism to launch the utility process from the zygote on Linux.jorgelo@chromium.org2011-12-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Allow the users of the utility process to specify whether the zygote should be used on Linux. This will allow sandboxing the uses of the utility process that don't do FS access. This is the first step to get the utility process sandboxed on Linux. Since most of the uses of the utility process don't do file access, launching all of those from the zygote will simplify sandboxing the one that does: extension unpacking. Subsequent CLs will port the uses of the utility process that don't do file access to launch from the zygote. BUG=93109 TEST=No functional changes yet, but test that nothing broke by running browser_tests::ExtensionWebstorePrivateApiTest.* and also logging into Chromium and installing an extension from the Web Store. Review URL: http://codereview.chromium.org/8849007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@113914 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 113027 - Zygote most of the uses of the utility process on Linuxdbeam@chromium.org2011-12-061-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | Allow the user of the utility process to specify whether the zygote should be used on Linux. This allows to sandbox all the uses of the utility process that don't do FS access, which right now are all except extension unpacking and NPAPI plugin listing. This is the first step to get the utility process sandboxed on Linux. Since most of the uses of the utility process don't do file access, launching all of those from the zygote will simplify sandboxing the one that does: extension unpacking. BUG=93109 TEST=Try installing an extension from the web store. Review URL: http://codereview.chromium.org/8770025 TBR=jorgelo@chromium.org Review URL: http://codereview.chromium.org/8817013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@113165 0039d316-1c4b-4281-b951-d872f2087c98
* Zygote most of the uses of the utility process on Linuxjorgelo@chromium.org2011-12-051-0/+1
| | | | | | | | | | | | | | | | | | | | | Allow the user of the utility process to specify whether the zygote should be used on Linux. This allows to sandbox all the uses of the utility process that don't do FS access, which right now are all except extension unpacking and NPAPI plugin listing. This is the first step to get the utility process sandboxed on Linux. Since most of the uses of the utility process don't do file access, launching all of those from the zygote will simplify sandboxing the one that does: extension unpacking. BUG=93109 TEST=Try installing an extension from the web store. Review URL: http://codereview.chromium.org/8770025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@113027 0039d316-1c4b-4281-b951-d872f2087c98
* Load mac sandbox definitions from resources instead of the bundle.jochen@chromium.org2011-11-251-0/+1
| | | | | | | | | | | Also, move all mac sandbox unittests to content BUG=90443 TEST=content_unittests Review URL: http://codereview.chromium.org/8589001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111614 0039d316-1c4b-4281-b951-d872f2087c98
* share all the needed linux code with OpenBSD in chrome and contentrobert.nagy@gmail.com2011-11-111-1/+1
| | | | | | | | | | | | | | disabled code for OpenBSD: - AdjustRendererOOMScore() - SECCOMP_SANDBOX BUG= TEST=compile Review URL: http://codereview.chromium.org/8341052 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109679 0039d316-1c4b-4281-b951-d872f2087c98
* Support --trace-startup and task tracingjoth@chromium.org2011-11-091-0/+7
| | | | | | | | | | | | | passing --trace-startup puts the tracing system into record mode immediately saving the result to chrometrace.log or a file specified by --trace-startup-file BUG=None TEST=start chrome with --trace-startup, wait 5 secs, see chrometrace.log in current dir. open it in chrome://tracing/ Review URL: http://codereview.chromium.org/7887013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109281 0039d316-1c4b-4281-b951-d872f2087c98
* Move content_restriction.h and main_function_params.h to ↵jam@chromium.org2011-10-311-16/+17
| | | | | | | | | content/public/common, and put them in the content namespace. BUG=98716 Review URL: http://codereview.chromium.org/8387039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108004 0039d316-1c4b-4281-b951-d872f2087c98
* Expose the sandbox related code through the content API. I did a bit of ↵jam@chromium.org2011-10-293-59/+19
| | | | | | | | | | | | | cleanup while I was doing this. -got rid of SandboxInitWrapper, since I didn't see a need to expose given that we can just expose sandbox::SandboxInterfaceInfo -got rid of the duplicated code to initialize the broker -since I made MainFunctionParams only have the sandbox struct on Windows, I also made the mac specific auto release pool behind an ifdef as well. It seemed odd to make something so mac specific compile on all platforms to save some #ifdefs. BUG=98716 Review URL: http://codereview.chromium.org/8414020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107863 0039d316-1c4b-4281-b951-d872f2087c98
* Move PageZoom enum into content/public/common and into the content ↵jam@chromium.org2011-10-281-1/+1
| | | | | | | | | namespace. Also move content_costants to content/public/common. BUG=98716 Review URL: http://codereview.chromium.org/8413051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107804 0039d316-1c4b-4281-b951-d872f2087c98
* Move ZygoteForkDelegateLinux to content/public/common.jam@chromium.org2011-10-251-3/+3
| | | | | | | BUG=98716 Review URL: http://codereview.chromium.org/8381029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107128 0039d316-1c4b-4281-b951-d872f2087c98
* Make setting the user agent work with the zygote on linux.dpranke@chromium.org2011-10-241-0/+9
| | | | | | | | | | | | | | | | | | Previously the user agent was set when we set the content client, which was set in the zygote, which didn't have a command line. Now, we still set the user agent in the zygote, but if the --user-agent command line switch is passed, we will reset the user agent in ZygoteMain. R=jam@chromium.org BUG=99418 TEST=run chrome with --user-agent=foo on linux, visit whatsmyuseragent.com, ensure 'foo' is displayed. Review URL: http://codereview.chromium.org/8296011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107012 0039d316-1c4b-4281-b951-d872f2087c98
* Move content_paths.h to content/public/common.jam@chromium.org2011-10-211-1/+1
| | | | | | | | BUG=98716 TBR=avi Review URL: http://codereview.chromium.org/8375007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106795 0039d316-1c4b-4281-b951-d872f2087c98
* Move ContentMainDelegate to content/public/.joi@chromium.org2011-10-203-131/+1
| | | | | | | | | | | | | Mostly a trivial move since the implementation for the class (now deleted) was do-nothing and the only subclass that didn't have a full implementation was ShellMainDelegate. BUG=98716 TEST=it builds + existing tests Review URL: http://codereview.chromium.org/8356025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106549 0039d316-1c4b-4281-b951-d872f2087c98
* Reland http://codereview.chromium.org/8233039/ with a fixdpranke@chromium.org2011-10-141-5/+5
| | | | | | | | | | | | so that mac works. TBR=jam@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/8276015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105439 0039d316-1c4b-4281-b951-d872f2087c98
* Move content_switches to content\public\common.jam@chromium.org2011-10-131-1/+1
| | | | | | | BUG=98716 Review URL: http://codereview.chromium.org/8277018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105389 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r105238 - "Link startup_helper_win statically to force ↵dpranke@chromium.org2011-10-131-5/+5
| | | | | | | | InitializeSandboxInfo" Review URL: http://codereview.chromium.org/8261002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105240 0039d316-1c4b-4281-b951-d872f2087c98
* Link startup_helper_win statically to force InitializeSandboxInfodpranke@chromium.org2011-10-131-5/+5
| | | | | | | | | | | | | | to use the sandbox library linked statically into an executable; using a sandbox library linked into content.dll doesn't work on windows. R=jam@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/8233039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105238 0039d316-1c4b-4281-b951-d872f2087c98
* Remove RenderProcessHost::is_extension_processjochen@chromium.org2011-10-051-1/+1
| | | | | | | | | | | | Also move the --process=extension command line flag to --extension-process BUG=89642 TEST=everything still works Review URL: http://codereview.chromium.org/8113035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104173 0039d316-1c4b-4281-b951-d872f2087c98
* Start off the Content API by moving content::ContentRendererClient to ↵jam@chromium.org2011-10-011-0/+4
| | | | | | | | | content\public\renderer. BUG=98716 Review URL: http://codereview.chromium.org/8100013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103609 0039d316-1c4b-4281-b951-d872f2087c98
* more content exports needed for unit_tests and browser_tests.dpranke@chromium.org2011-09-301-1/+1
| | | | | | | | | | R=jam@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/8082019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103584 0039d316-1c4b-4281-b951-d872f2087c98
* add exports needed for content_shelldpranke@chromium.org2011-09-291-1/+4
| | | | | | | | | | R=jam@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/8071017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103344 0039d316-1c4b-4281-b951-d872f2087c98
* Export more symbols needed for the component build of content.dpranke@chromium.org2011-09-161-1/+2
| | | | | | | | | | R=jam@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/7885041 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@101443 0039d316-1c4b-4281-b951-d872f2087c98
* Move the V8 benchmarking_extension.cc/.h files out of webkit/extensions into ↵ananta@chromium.org2011-09-151-2/+1
| | | | | | | | | | | | | | | | | | | chrome as the functionality exposed by this extension is chrome specific. The IPCs used by this extension have all been moved to chrome to a new header file benchmarking_messages.h in chrome\common. Added a new message filter object in chrome\browser which filters the benchmarking IPCs. Most of the changes in this CL are centered around ensuring that the benchmarking stuff gets initialized in the same order as before. Continuing changes to get rid of the pattern of IPC messags spanning across content and chrome. BUG=87335 Review URL: http://codereview.chromium.org/7885013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@101214 0039d316-1c4b-4281-b951-d872f2087c98
* fix const decl in content_main.dpranke@chromium.org2011-09-131-1/+1
| | | | | | | | | | TBR=jam@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org/7889019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100979 0039d316-1c4b-4281-b951-d872f2087c98
* Annotate all of the functions in content that need to be exported, in ↵dpranke@chromium.org2011-09-131-6/+7
| | | | | | | | | | | | preparation for creating a content shared library. R=darin@chromium.org, jam@chromium.org, willchan@chromium.org BUG=90442 TEST=everything still compiles Review URL: http://codereview.chromium.org/7800015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100975 0039d316-1c4b-4281-b951-d872f2087c98
* export RendererMain from content so that it will get picked up properly by ↵dpranke@chromium.org2011-09-131-1/+1
| | | | | | | | | | | chrome_main. R=jam@chromium.org BUG=90442 Review URL: http://codereview.chromium.org/7841009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100809 0039d316-1c4b-4281-b951-d872f2087c98
* Basic scaffolding for a "content shell", i.e. test browser over the content ↵jam@chromium.org2011-09-124-12/+71
| | | | | | | | | | | module. Once it's working, this will allow developers working on the core chrome code/web platform/networking etc to test their changes on a much smaller and hence faster to build/run/debug browser. This doesn't do anything yet because it's blocked on having TabContentsView implementations in content. BUG=90445 Review URL: http://codereview.chromium.org/7857019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100778 0039d316-1c4b-4281-b951-d872f2087c98
* Make the NaCl windows 64 bit binaries not depend on chrome targets. These ↵jam@chromium.org2011-09-125-87/+104
| | | | | | | | | | | | | targets are very simple and used little code from chrome targets. However their dependency on chrome targets was problematic because a lot of code wasn't being built for 64 bit on Windows, and so there were a lot of "dummy" files being added with stub functions and code was also being compiled out in random places for NACL_WIN64. I've made the NaCl 64 bit windows targets self contained. They do use a few files from common, but those files are self-contained. In the future, we could move these to be in the same 64 bit target as the constants from common. However that won't make a maintenance difference since someone could still introduce link dependencies to other files in common. Additionally, since we're not using chrome code anymore, we can avoid having both nacl.exe and nacl.dll. nacl.exe is sufficient, and this saves 1.4MB of uncompresed binaries in the installer. BUG=86322 Review URL: http://codereview.chromium.org/7863024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100767 0039d316-1c4b-4281-b951-d872f2087c98
* Fix use-after-free of command line data on Linux/CrOSjamescook@chromium.org2011-09-091-1/+1
| | | | | | | | | | | Typo in content_main.cc RunZygote was using an old pointer to the command line data. BUG=95620 TEST=Address sanitizer no longer shows use-after-free in browser_tests RenderProcessHostTest.ProcessOverflow Review URL: http://codereview.chromium.org/7857036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100430 0039d316-1c4b-4281-b951-d872f2087c98
* Start moving code from BrowserMain to content, so that it can be reused by ↵jam@chromium.org2011-09-071-0/+52
| | | | | | | | all embedders of content. I've based the refactoring on the existing BrowserMainParts. This is the first step; I didn't want to do it all at the same time because it would be too big. Remaining tasks:-rename the browser_main files in chrome to chrome_browser_main-move the OS specific implementations of BrowserMainParts that are needed for content-finish splitting the remaining BrowserMain function (now that's in TemporaryContinue())BUG=90445 Review URL: http://codereview.chromium.org/7779040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99884 0039d316-1c4b-4281-b951-d872f2087c98
* Finish moving all the generic startup code from ChromeMain to ContentMain, ↵jam@chromium.org2011-09-023-30/+340
| | | | | | | | | and add callbacks to ContentMainDelegate to handle the Chrome specific pieces. BUG=90445 Review URL: http://codereview.chromium.org/7792080 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99452 0039d316-1c4b-4281-b951-d872f2087c98
* Start moving ChromeMain code to content so it can be reused by other ↵jam@chromium.org2011-09-016-0/+294
embedders. I've only moved a little bit of the code for now, and will do the rest in followup changes. BUG=90445 Review URL: http://codereview.chromium.org/7817015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99193 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-06 10:44:08 +0000