Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hard crash on adding folder #183

Closed
hsoft opened this issue Jun 22, 2013 · 4 comments

Comments

Projects
None yet
1 participant
@hsoft
Copy link
Collaborator

commented Jun 22, 2013

I experienced a hard crash on adding a folder to dupeGuru PE 2.3.0 and I can reproduce it although I haven't identified the underlying cause yet.

  1. Launch the app with 2 restored folders: ~/Downloads and iPhoto Library. iPhoto Library is in an Excluded state.
  2. Select the ~/Download folder and click the "-" button.
  3. Select the iPhoto Library item and click the "<" button which replaced the "-" button (to un-exclude).
  4. Click on the "-" button.
  5. Click on the "+" button.
  6. In the file dialog, select the ~/Downloads folder and click open.
  7. Crash

The log is attached.

@hsoft hsoft closed this Jun 22, 2013

@hsoft

This comment has been minimized.

Copy link
Collaborator Author

commented Jun 22, 2013

It really has something to do with two root folders with the second being the iPhoto Library in excluded state. I tried a couple of other possibilities (another folder in excluded state, the iPhoto Library in normal state, etc) and I didn't get the crash. On point 6 however, it's not important that it's the ~/Downloads folder that is being added. I tried another folder and it crashed too.

@hsoft

This comment has been minimized.

Copy link
Collaborator Author

commented Jun 22, 2013

Oh, here's something interesting: This crash doesn't happen in 32-bit mode.

It looks like I'll have to update to the latest version of pyobjc (I see in the changelogs that libffi was updated to fix x86_64 issues). I hope that it will not cause too much troubles.

@hsoft

This comment has been minimized.

Copy link
Collaborator Author

commented Jun 22, 2013

I updated pyobjc on my dev machine to the repo's tip (eebec14eca41) and it fixed the problem. There have been many changes in pyobjc in between this version and the one that I was using before (namely a big and cool-looking change in the way metadata is handled) so I hope it will not cause new problems, but I'll try it for a while before I update pyobjc on my build machine (and I'll set the ticket as fixed after I've updated the build machine).

@hsoft

This comment has been minimized.

Copy link
Collaborator Author

commented Jun 22, 2013

I've updated the OS X build machine to pyobjc's current tip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.