Steps to reproduce (not that simple and I'm not completely sure which steps are relevant)
I have two Mac-accounts with one instance of N1 running on each account. The first installation of N1 happend on the first account.
On the first account I installed the N1 0.4.16 update
I sent the Mac to sleep
I waked the Mac up
The CPU load of the N1 instance on the second Mac-account moved around 100 % (see screenshot 1)
On the second account the N1 update helper installation screen was opened and waited for input (see screenshot 2)
After entering my credentials the update notification appeared in N1 (even though it was already up to date because of the update on the first account)
The CPU load dropped to a normal level after I entered my account credentials
Install nowclosed N1 but did not restart it. However, this often happens with programs that were installed on a different account. It's the same for GitHub for Mac for example.
After restarting N1 everything is back to normal
Screenshot 1
Screenshot 2
Are there any related issues?
No
What operating system are you using?
OSX 10.11.4 Beta (15E49a)
What version of N1 are you using?
0.4.14 -> 0.4.16
Bug?
Do you have any third-party plugins installed?
Some themes on both accounts, squirt-reader on the first account
Is the issue related to a specific email provider (Gmail, Exchange, etc.)?
No
Is the issue reproducible with a particular attachment, message, signature, etc?
Steps to reproduce (not that simple and I'm not completely sure which steps are relevant)
0.4.16
updateInstall now
closed N1 but did not restart it. However, this often happens with programs that were installed on a different account. It's the same for GitHub for Mac for example.Screenshot 1
Screenshot 2
Are there any related issues?
No
What operating system are you using?
OSX
10.11.4 Beta (15E49a)
What version of N1 are you using?
0.4.14
->0.4.16
Bug?
Do you have any third-party plugins installed?
Some themes on both accounts,
squirt-reader
on the first accountIs the issue related to a specific email provider (Gmail, Exchange, etc.)?
No
Is the issue reproducible with a particular attachment, message, signature, etc?
See above