Debugging update
When I finish my long "stop estrip from crashing on Safari" journey, I'll probably write a long post about it with all the stupid details. But for the time being, I'll probably use this journal to keep track of how far long I am.
Step 1 Summary
Yesterday, I fired up my powerbook in a fresh reboot and ran only Safari with e-strip loaded on it without having visited any prior sites. I left the machine to sit there idly the entire day I was at work. When I came home and turned on the monitor, I see a crash dialog.
From this experiment, I can most likely conclude that there's nothing special I have to do, such as being in the middle of a post or writing a comment, for Safari to crash on (e:strip). And this is great, which means that there's a lot less slightly different iterations of things I'm going to have to test to get the crashes to happen.
Step 2 will being fashioning a simple, estrip only web browser with webkit, the underpinnings of Safari, and that browser to estrip and leaving it and seeing if it crashes. If it doesn't crash, then that likely means there's some problem with the Safari executable itself and the webkit libraries it uses are okay, although I think that is pretty unlikely.
Step 1 Summary
Yesterday, I fired up my powerbook in a fresh reboot and ran only Safari with e-strip loaded on it without having visited any prior sites. I left the machine to sit there idly the entire day I was at work. When I came home and turned on the monitor, I see a crash dialog.
From this experiment, I can most likely conclude that there's nothing special I have to do, such as being in the middle of a post or writing a comment, for Safari to crash on (e:strip). And this is great, which means that there's a lot less slightly different iterations of things I'm going to have to test to get the crashes to happen.
Step 2 will being fashioning a simple, estrip only web browser with webkit, the underpinnings of Safari, and that browser to estrip and leaving it and seeing if it crashes. If it doesn't crash, then that likely means there's some problem with the Safari executable itself and the webkit libraries it uses are okay, although I think that is pretty unlikely.
But this is weird.