Activity for Tobias Netzel
-
Tobias Netzel posted a comment on ticket #121
Well, no idea about the API the Safari IOS app uses for interfacing with the WebKit frameworks. For Leopard I "only" needed to maintain the classic WebKit Objective-C API compatible with the Safari application - no WebKit2 APIs fortunately. There were rather few point where I had to do something user interface related, since the user interface is almost entirely provided by the application which uses the WebKit API for rendering web pages.
-
Well, I've got no idea at all. I bet it would take many months to get anything to even launch at all.
-
I don't know the current state because I haven't been using leopard-webkit for some time. But I used to relink the Leopard Mail application using the relink droplet and that way could still connect reasonably well to a variety of e-mail services. Gmail needed to have improved connection security switched off for Leopard Mail to be able to connect.
-
Plain old internet has become enormously complicated over the decades - and unfortunately I'm not working any longer on leopard-webkit. My iMac G5 has died some time ago...
-
Plain old internet has become enormously complicated over the decades - and unfortunately I'm not working any longer on leopard-webkit.
-
Well, I have been collaborating with Cameron Kaiser in his TenFourFox project - especially with the Altivac enhancements. Unfortunatelay it's quite difficult to use a different TLS library in WebKit on OS X because WebKit itself doesn't use TLS directly but indirectly via OS framework interfaces. Generally WebKit uses OS interfaces whereever possible while Firefox uses its own code whereever possible. That way WebKit is deeply integrated into the OS, making it particularly difficult to replace something...
-
No update in the works. I had the 605 merge halfway done but never finished it. I fear this is the end of Leopard WebKit - the biggest problem being in fact the lack of modern TLS cipher suites, making more and more sites inaccessible. While updating the WebKit core would be feasible (for me), updating the TLS cipher suites would be a project of its own.
-
No update in the works. I had the 605 merge halfway done but never finished it. I fear this is the end of Leopard WebKit - the biggest problem being in fact the lack of modern TLS cipher suites, making more and more sites inaccessible.
-
Yes, it's dead unfortunately.
-
The problem with https (TLS) is the lack of modern secure ciphers. Leopard WebKit did come with the latest ciphers Apple shipped with later versions of OS X but unfortunately Apple had switched to an entirely different TLS stack some years ago leaving us without any code to backport (in fact only because of that switch the old code was open sourced by Apple and made possible updating the TLS stack used in Leopard WebKit at all).
-
Chances are good that the instability of Safari 5.0.5 on 10.6.8 is mainly caused by the WebKit version coming with it. Did you also test Safari 5.0.5 running with Leopard WebKit 537?
-
BuildInstructionsSecurity
-
BuildInstructionsSecurity
-
BuildInstructionsSecurity
-
BuildInstructionsSecurity
-
BuildInstructionsSecurity
-
Those missing files should be created by applying the patch. Maybe you forgot to use '--strip 3' instead of '--strip 2'?
-
Hi Finn! Great to see some interest in this project after such a long time. My only NuBus-PowerMac (a PowerBook 1400 with G3 upgrade) has died only recently so I can't even do any testing for this project anymore. So I'd like to add you as a project admin as you seem to be able and willing to work on it. What do you think?
-
Thanks! Yes, a 32 bit Intel Snow Leopard build is indeed needed - but there's still missing some volunteer to get it built and tested on Snow Leopard. I simply don't own any machine capable of running it. I hope work on the Snow Leopard build will start again soon! Tobias
-
Hi David, that's really great news! A couple of hours per week should be sufficient. So please create s sourceforge account so we can get in contact directly and also use the ticket system here. Best Regards, Tobias Netzel
-
Well, in case it is listed as an Intel application it must have loaded the version of the WebKit frameworks currently installed; the "About Safari" window might reveal which version of WebKit is being used; in case of Leopard WebKit 601 it should show "601+" where mine Version 5.0.6 (5533.22.3, 603+) says "603+", though I don't know whether Safari 5.1 does this the same way as Safari 5.0.6 did.
-
Out of curiosity; why don't you upgrade to 10.6.8? 601 is PowerPC only so you're running it in Rosetta (emulated PowerPC G4 CPU).
-
Thanks for the offer - but as I don't have any 10.6 compatible system I cannot even produce any beta build for 10.6 . And it's simply too much for one single person, maintaining a build for both 10.5 and 10.6 .
-
Im Dateinamen steht "Leopard-PowerPC". Auf der "Summary"-Seite steht OS X 10.5 PowerPC und dass Freiwillige für ein Wiederbeleben der Snow-Leopard-Version benötigt werden (ich selber besitze nur PowerPC-Macs, einen G4 und einen G5). Es gibt natürlich alte Versionen, die zwar unter Snow-Leopard laufen, aber so alt sind, dass es besser ist, nicht darauf hinzuweisen. Das letzte verbliebene "(Snow)" aus dem Untertitel des Projekts wollte ich noch nicht streichen, da ich immer noch die Hoffnung habe,...
-
As David experienced serious bugs with extensions in Safari 5.0.5 in 10.6.8 (latest version using the legacy WebKit which is backported by this project), he has appearently lost interest in continuing the Snow Leopard port.
-
It should work - but currently only using Rosetta (PowerPC emulation). I haven't been doing native Intel builds for some years now.
-
It should work - but currently only using Rosetta (PowerPC emulation). I haven't been doing native Intel builds for some years now.
-
Hi! I did use it with admin accounts exclusively, and on my two Macs I didn't have any such problem yet. And you don't get any error dialog?
-
604.5.6_2 is now available for download! Please report how well it works for you.
-
Home
-
Home
-
Home
-
I don't know this particular issue - though I do have an unreleased version of Leopard-WebKit that you might try. I'll let you know when it's ready for download. Any specific steps for reproducing this bug? Do you have any Safari add-ons, extensions or plugins installed?
-
Well, there is Roccat, but that's only the browser and not the HTML, DOM, CSS or JavaScript libraries (which is the part that WebKit does). Updating WebKit upgrades Safari's or Roccat's web capabilities to the level of newer versions of OS X. But TenFourFox will probably come to Intel OS X sometime this year I guess.
-
Snow Leopard was supported until the 537 series. Some volunteers tried porting later series but lost interest when it became clear that it would cost them too much time for not even achieving Safari 5.1 support (but only 5.0.5). The wiki page states that 10.6 support is a goal of this project - an unreached one unfortunately.
-
Snow Leopard was supported until the 537 series. Some volunteers tried porting later series but lost interest when it became clear that it would cost them too much time for not even achieving Safari 5.1 support (but only 5.0.5).
-
The non-relinked Safari isn't able to access many https sites nowadays because of its weak encryption capabilites being denied by the servers. Could you please verify whether you can access the affected sites (those that stay black) using the original Safari?
-
The WebKit application will always force Top Sites to use Leopard WebKit - and in the latest release I changed the relinking droptlet to relink Top Sites as well. So the behavior of both is now identical. You might try replacing the relinked Top Sites preview renderer with the original one: In the Finder you should open both the relinked and the original Safari applications (right click and tell it to show package contents). Then open the "Contents" folder of both and drag the "Safari Webpage Preview...
-
Well, Top Sites has quite low priority for me - I'm happy as long as it doesn't crash. The memory issues seem far more important to me - and I'm going to start work on the 605 series now, which will keep me busy for quite some time.
-
Any application using OS X WebKit for rendering web pages could be relinking to use Leopard WebKit instead. The relinking droplet will tell you if the application you dropped on it wasn't linked against OS X WebKit. I regularly use it for relinking Mail, Safari, Roccat and Stainless. I can't spot any direct relation to Leopard WebKit in that crash report, but it would be of use to me if you knew how to reproduce it.
-
Home
-
604.5.6 is ready! TopSites should work now, both with a relinked Safari and the WebKit application. Please report your results! (And don't forget to clean up and/or replace any previous relinked applications!)
-
Safari top site previews are indeed broken in the 604 release because Apple had removed a bit of code from WebKit which our old Safari needs for rendering the preview images. So for many sites preview rendering crashes in the background when trying to render. I'll try to upload a fixed version within the next few hours.
-
In your case I'd recommend to delete all Safari applications from your applications folder and reinstall from the dmg. And as the relinking process doesn't always succeed - depending on the current Finder activity - I think you should stay away from that and use the WebKit applications instead.
-
You might want to relink against 604, instead of the 603,3,3 the crashed "Safari LepWK.app" is relinked against. For that purpose you'll need the original non-relinked one. Or just use the WebKit app from the 604 disk image.
-
You should definitely reinstall Safari 5.0.6 - both your Safari applications are relinked ones. Be sure you always keep an unmodified backup in order to be able to restore the original "Safari.app".
-
As it seems your "Safari.app" is a relinked one. The unmodified one has a size of 54 MB here. I'm always using a relinked copy of Safari. In case you prefer the WebKit application I recommend to make sure that your "Safari.app" is unmodified.
-
Do you know of specific sites that cause WebKit to quickly crash with exception type EXC_BREAKPOINT (SIGTRAP)? That might help me to finally fix that nasty memory leak.
-
Hmm, I got this same crash occasionally, but I have no idea what to do against it - there's no WebKit/WebCore/JavaScriptCore function in the backtrace for the crashed thread. If there was a way to trigger this one, I might be able to fix it. Do you happen to get this one (crashing in "0 libobjc.A.dylib 0xfffeff20 objc_msgSend_rtp + 32") frequently?
-
... no more memory/address space available.
-
... no more memory/address space available.
-
What kind of streams? Can I test those streams myself?
-
This crash seems to have happened because some operating system function couldn't allocate any more memory - so the cause is probably a WebKit memory leak as well.
-
The crashes of type EXC_BREAKPOINT (SIGTRAP) do generally happen because of WebKit being unable to allocate more memory. Although you previously had 8 GB of total memory 32 bit applications like Safari 5.0 can make use of up to 4 GB only. There is probably a memory leak in WebKit, but I couldn't find the cause yet. Maybe there can only be one anonymously uploaded file awaiting moderation at the same time. But please upload or copy and paste your crash reports (in case you didn't know: you find them...
-
Marking as invalid because this issue is not under control of WebKit.
-
Closing tab does not default to previous tab
-
Thanks for reporting!
-
Safari Preview unstable with WebKit
-
You're definitely right! What about SSH access to that dedicated build machine? That machine should have at least 2 GB of RAM and 40 GB of free hard disk space.
-
Since 601 Leopard WebKit brings its own versions of GCC and C++ runtime libraries, that might prevent it from being run in Rosetta The only solution in your case would be a 10.5 Intel build - while that should be quite easy to do, it would take quite some days for building GCC. And to me it seems a 10.6 Intel version would make much more sense since there seem to be far more people running 10.6 on Intel Macs.
-
Google will have fixed their javascript code to not call non-existing APIs. Nevertheless the next release will have that API enabled, preventing possible future problems.
-
It was because of Google depending on some javascript/DOM timing API features. The timing API itself is optional but Google image search does not test for availability before using it - so the script fails with uncaught exception errors and the images are never shown. I had disabled the timing API because OS X 10.5 doesn't support all of the required features. Now I enabled it but some of the API calls won't ever return anything but default values. The next release of Leopard WebKit will come with...
-
It doesn't work for me either, I'll try to figure it out - but it may be quite difficult.
-
'vmmap' provides a lot of information - those lines are the most summarized output from it. It is actually possible to log all memory allocations by sourcecode line - but it needs some GB of free RAM for not taking the whole night (constantly swapping memory between the hard drive and RAM). So using those tools would only be possible on a PowerMac G5 - which I don't own.
-
I just gave it a try by doing that search on ebay in the Safari session that I've been using since yesterday. I used the command line developer tool 'vmmaps' for examining Safari's memory usage. Before opening those ebay pages the following summarized values were determined: Writable regions: Total=1.4G written=822.3M(59%) resident=956.0M(69%) swapped_out=9856K(1%) unallocated=428.7M(31%) After opening and fully loading those pages the values were like this: Writable regions: Total=1.4G written=836.9M(60%)...
-
Home
-
Just for providing some background information: WebKit doesn't immediately free memory when closing tabs or windows because it keeps the "pages" in its page cache. A certain number of pages are always kept in that cache; if I remember correctly Roccat sets a smaller page cache size than Safari. So the observed behaviour is to be expected - to some extent.
-
Would be absolutely great if you could provide steps for reproducing it that quickly! I've seen this happen quite frequently but I don't know how to reproduce it - the browser uses to run rather well for quite some days. But if you could tell me a trick to quickly force this I'hopefully be able to finally find and fix the issue! Please tell me what sites you're visiting and whether you are using Safari extensions like ad blockers or Safari hacks like Glims (which I've been using for several years)....
-
Would be absolutely great if you could provide steps for reproducing that so quickly! I've seen this happen quite frequently but I don't know how to reproduce it - the browser uses to run rather well for quite some days. But if you could tell me a trick to quickly force this I'hopefully be able to finally find and fix the issue! Please tell me what sites you're visiting and whether you are using Safari extensions like ad blockers or Safari hacks like Glims (which I've been using for several years)....
-
Webkit Memory Leak ?
-
The WebKit application used to be Apple's means to deliver WebKit nightliy builds to testers. It launches Safari, temporarily relinking to the updated WebKit frameworks contained in the WebKit application bundle. It does also add an automatic update mechanism - which doesn't work for Leopard WebKit. So it shouldn't matter which of both methods for using Safari with Leopard WebKit you choose. But you might want to try the fresh 604 release (look for it on the "Files" tab), as that should fix Top Sites...
-
Thanks! Just corrected that.
-
Home
-
Please report whether this is still an issue for you with the 604 release!
-
The new 604 release should fix the "Safari Webpage Preview Fetcher" crashes.
-
Home
-
You'll need libc++ from clang since system libstdc++ lacks support for C++11 and later. Don't bother following the build instructions in the wiki. You should instead just get a subversion checkout of Safari-604.3.4 as described in the wiki. You'll also need git in order to apply the patch I'll hopefully upload soon.
-
This seems to be [#115]. You should get previews working by using a relinked Safari application instead of the WebKit application. Make sure your system is as idle as possible, drag your Safari application and drop it over the "Relink against Leopard WebKit" droplet that comes with Leopard WebKit. Then wait until the doplet's icon disappears from the Dock - you should not use your Mac while the droplet is doing its work, as it may fail then.
-
Well, unfortunately the automatic update messages don't work for Leopard WebKit - they work (or at least used to work) for Apple's WebKit releases exclusively. I just used their WebKit application (a Safari launcher in fact) as it was when they released it for 10.5 for the last time. You need to check the Leopard WebKit project web site in order to know when there are updates. All in all Leopard WebKit is not very convenient for the average user who doesn't care of the inner workings of applications...
-
I know that behavior - but I haven't investigated yet whether it's a bug or intended like this.
-
Link from history missing when going back one page
-
As WebKit largely depends on C++11/14/17 features you'd need to use a later version of clang. David used clang-3.8.1 and that proved to work. But be warned; it'll take some weeks until the first completed build. In case you seriously consider doing the build, I'll post the results of David's work here - and we got pretty far. And you need to keep in mind that you can't use Safari 5.1; browser options to be considered are Safari 5.0.5, Roccat and Stainless.
-
As WebKit largely depends on C++11/14/17 features you'd need to use a later version of clang. David used clang-3.8.1 and that proved to work. But be warned; it'll take some weeks until the first completed build. In case you seriously consider doing the build, I'll post the results of David's work here - and we got pretty far.
-
This is indeed because of Growl - it can't deal with being invoked by certain background tools like "Safari Webpage Preview Fetcher". I found a workaround and will either release it in a last 603 version or in the upcoming 604 series. A relinked Safari will not cause that problem - for now I'd recommend to either disable preview rendering using the supplied script or using a relinked Safari application.
-
I know there are still some cases of badly rendered/characters - but as the linked case renders the same in Leopard WebKit, stock Safari 5.0.6 and even TenFourFox, I suspect it's the web site itself which causes the bad rendering. Do you happen to have other examples?
-
Text crumpled corruption in web sites
-
I know there are still some cases of badly rendered/characters - but the linked case renders the same in Leopard WebKit, stock Safari 5.0.6 and even TenFourFox. Do you happen to have other examples?
-
Thanks for the crash report - this one is interesting but the cause isn't obvious (it might be related to Growl though, see here). It should not happen when using a relinked Safari because "Safari Webpage Preview Fetcher" will not be using Leopard WebKit in that case - but as the system default WebKit renders modern web pages more or less badly the previews won't look correctly.
-
Thanks for the crash report - this one is interesting but the cause isn't obvious (it might be related to Growl though). It should not happen when using a relinked Safari because "Safari Webpage Preview Fetcher" will not be using Leopard WebKit in that case - but as the system default WebKit renders modern web pages more or less badly the previews won't look correctly.
-
The QuickLook daemon crashes shouldn't be related to Leopard WebKit at all; it's simply QuickTime crashing when trying to scan certain media files it wasn't prepared for. There's no trace of WebKit or JavaScriptCore anywhere in the crash report (it wasn't even loaded when the crash occurred). Would be nice though if you could find some sample files that cause these crashes - maybe we can find a workaround for these nasty crashes. I guess you should try removing any media files (video and audio) from...
-
Safari Preview unstable with WebKit
-
As David experienced serious bugs with extensions in Safari 5.0.5 in 10.6.8 (latest version using the legacy WebKit which is backported by this project), he has appearently lost interest in continuing the Snow Leopard port.
-
http://trac.webkit.org/changeset/219050/webkit removes Yosemite support
-
http://trac.webkit.org/changeset/212211 removes a lot of checking for unimplemented Objective-C methods
-
Home
-
BuildInstructions
-
The latest version is available here: https://sourceforge.net/projects/leopard-webkit/files/537/%28Snow%29%20Leopard/WebKit-537.78.2_4-%28Snow%29Leopard.dmg/download It's more or less equal to what shipped with Safari 7 (OS X 10.9). Follow the instructions to install Safari 5.0.5 as it won't work with Safari 5.1 .
-
Snow leopard compatible version?
-
Well, an Intel build would be easliy done - but a 10.6.8 build needs quite some work to get it working right. In order to have it build and work on 10.5.8 one has to disable/workaround/reimplement things that require OS support relying on feature that were introduced in more recent OS versions only. Obviously for 10.6.8 many of the same things that apply to 10.5.8 also apply but others don't and again others would have to be solved differently. After all WebKit, contrary to Firefox, integrates into...
1 >
