Merge contact record of currently logged in user hangs

If you are logged in as admin and try to merge your own record (the one linked with your drupal account) the page hangs and is never loaded. The problem happens when the cid in the merge URL is the cid of the currently logged in admin.

For example, this page hangs and never loads, if user with cid of 102 is currently logged in and requesting the page:

http://my.website.com/civicrm/contact/merge?reset=1&cid=102&oid=15334&action=update&rgid=1

The reverse has a different (possible?) problem--the page loads and the merge success but a message comes up indicating that the currently logged in user's contact info can't be deleted. Even though the merge has been successful and the currently logged in user's contact info has in fact been deleted!

This happens, for example, when the currently logged in admin is cid 102 and loads and submits this page:

http://my.website.com/civicrm/contact/merge?reset=1&cid=15334&oid=102&action=update&rgid=1

Trying the similar thing on the drupal6.demo web site, there is a slightly different problem and error message, but still (I think) some kind of underlying problem. On the demo site, logged in as cid=103 this page loads fine:

http://drupal6.demo.civicrm.org/civicrm/contact/merge?reset=1&cid=103&oid=602&action=update&rgid=1

But trying the reverse (or clicking 'switch between original and duplicate" on the page above), like loading this page:

http://drupal6.demo.civicrm.org/civicrm/contact/merge?reset=1&cid=602&oid=103&action=update&rgid=1

leads to a puzzling error message:

The error message is "The contact record which is linked to the currently logged in user account - 'demo@civicrm.org' - cannot be deleted. No possible duplicates were found using IndividualFuzzy rule." and the error takes you to http://drupal6.demo.civicrm.org/civicrm/contact/deduperules?reset=1 rather than back to the contact editing you were in the middle of, or back to the merge you were in the middle of.

The first part of the error message of course makes sense (if indeed the currently logged in user cannot be deleted) but the second part about no possible duplicates is nonsensical.

This is under Drupal 6 and CiviCRM 4.2.