Bug 15889 – Drosera Fails to Launch on Tiger with a dyld error

• Status: CLOSED
• Resolution: FIXED
• Component: New Bugs

[Evan Stone]

I attempted to launch Drosera on last night's Nightly Build (build number r27504), and Drosera did not launch - it "bounced" once in the dock and then nothing. I tested this back a few versions and found the same problem, so I went back to build r26919, just to see if it was a problem with my system. 

The good news is that r26919 launched properly, so somewhere between r26919 and r27504 there seems to be a breakage in the launching of the Drosera app. I kept testing and found that things started to go a little funny around r27021, since it launched, but then quit after attempting to attach to WebKit. Going back one more version, r26989, the problem stopped: WebKit launched, Drosera launched, and I was successfully able to attach without it crashing (I have not tested debugging with that version yet, since I'm just trying to find one that works, but I'll attach a  comment if I find anything else that's wonky...).

Here's a summary of the versions I tested and the results:

r27504: Drosera failed to launch.
r27464: Drosera failed to launch.
r27106: Drosera failed to launch.
r27031: Drosera failed to launch. 

NOTE: The interesting thing here is that the versions start failing outright at the same time that the size of the download doubles... Just thought I'd throw that observation in - hope it's helpful.

continuing...

r27021: Drosera launches, shows "Attach" dialog, and after selecting "WebKit" and clicking "Attach," it immediately crashes with a "DroseraLauncher quit unexpectedly" dialog. But hey, at least it launched.

r26989: Drosera launches and stays active without crashing.
r26961: Drosera launches and stays active without crashing.
r26919: Drosera launches and stays active without crashing.


Vital Statistics:

* Dual 1.8 GHz PowerMac G5
* Mac OS X 10.4.10
* 2 GB RAM


NOTE: Just for kicks I tried launching r27504 on my 17" MacBook Pro, and while Drosera launched and _seemed_ to attach correctly, it bombed ("Unexpectedly quit") after navigating to another page. So it seems that problems are not isolated to PPC (just a different effect on Intel).

[Mark Rowe (bdash)]

Pretty sure this is my fault.  Chances are I made an error when tweaking Drosera to work with the super-fat Leopard/Tiger nightly builds.

[Mark Rowe (bdash)]

Thanks for the detailed bug report Evan!  It made tracking down the issue really easy.  I've made the fix in the scripts used to build the WebKit nightlies, and a new build should be available in the next half hour with a version of Drosera that works on 10.4.   It'll most likely be based on r27582.

Thanks again!

[Evan Stone]

Glad to help! 

I figured the more information you had the easier it would be to track down. Thanks for handling the situation so quickly too!

[Timothy Hatcher]

Closing since Drosera has been replaced by the new Web Inspector debugger. Moving to the New Bugs component so the Drosera component can be closed and removed.