Running into an issue when I route from one Route to another. Both routes have a subscription to a user publisher.
However, the first Route subscribes to a Client side only collection, with around 2300 users.
When I route to another Route, the contact list, which has a subscription to all users with a limit of 20, Chrome browser hangs for 10 seconds and then starts rendering the list with a lot of undefines. Then it repaints and the list is correct.
So what happens is this: when I move away from the first page, the subscription should automatically be removed. (I even called the .stop() in the template.destroyed handler).
However, when I directly route to the Contact list it subscribes to users again (different subscription though). Apparently it cleaning the current subscription runs into a conflict with adding the new users to mini mongo.
Interesting enough, when I go from Route 1 (with the big client side collection only) to a Route 3, one that has a Composite subscription of classes with a child subscription of users (only 8), this loads immediately.
This is probably because the subscription is small, however Route 2 with the Contact list subscription has a limit of 20. So the client should also receive a small collection.
Am I running into a Meteor issue here?