WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
44537
WebKit2 should launch the WebProcess in 32-bit mode if the UIProcess is in 32-bit mode
https://bugs.webkit.org/show_bug.cgi?id=44537
Summary
WebKit2 should launch the WebProcess in 32-bit mode if the UIProcess is in 32...
Sam Weinig
Reported
2010-08-24 10:53:25 PDT
WebKit2 should launch the WebProcess in 32-bit mode if the UIProcess is in 32-bit mode
Attachments
Patch
(2.61 KB, patch)
2010-08-24 19:47 PDT
,
Sam Weinig
mrowe
: review+
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Sam Weinig
Comment 1
2010-08-24 10:53:59 PDT
<
rdar://problem/8348100
>
Sam Weinig
Comment 2
2010-08-24 19:47:18 PDT
Created
attachment 65362
[details]
Patch
Mark Rowe (bdash)
Comment 3
2010-08-24 20:05:20 PDT
Comment on
attachment 65362
[details]
Patch
> + > + posix_spawnattr_t attr; > + posix_spawnattr_init(&attr); > + > +#if CPU(X86) > + // We spawn a 32-bit child process if the host is 32-bit. This allows checking > + // the "Open in 32-bit mode" check box in the finder and getting a 32-bit WebProcess.
I don’t like the way this comment is worded. It would be better to say something about having the child process run as the same architecture as the parent process. The Finder in particular isn’t all that interesting here.
> + cpu_type_t cpuTypes[] = { CPU_TYPE_X86 }; > +#else > + cpu_type_t cpuTypes[] = { CPU_TYPE_ANY }; > +#endif > + size_t outCount = 0; > + posix_spawnattr_setbinpref_np(&attr, 1, cpuTypes, &outCount);
You could move this call in to the #if and drop the #else completely. r=me
Sam Weinig
Comment 4
2010-08-24 20:11:20 PDT
Landed in 65968.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug