While troubleshooting a misbehavior in Spree where the product list was not paginating and was only listing the first 10 products or so, I attempted to reproduce the error in my local development environment and on the first page load I received the error:
ArgumentError (dump format error)
As always, I checked my other brain first. The top search result was: https://github.com/rails/rails/issues/2509
Although the the user who started that thread and several of the other posters were attempting an upgrade from Rails 3.0.9 to Rails 3.1, I didn’t think it would apply to my case. The Spree 0.60.2 app I’m running is at Rails 3.0.9.
However, as it turns out, simply clearing my localhost cookies solved the problem. Why?
I’m going to speculate that because I’m running multiple applications in my development environment, including a Rails 3.1/Spree 0.70 version of the same app, and I visit all of them via localhost, that there was a conflict of some sort in the cookies, where the 3.1 version set some cookie that the 3.0.9 version couldn’t eat. It probably has to do with what @Fjan mentioned in his post here (https://github.com/rails/rails/issues/2509):
I ran an experiment. Provided I did not login on either version of the app, I could start one up and shut it down and start the other and not run into this problem on either. However, when I logged into the 3.0.9 version and then shut down that server and launched the 3.1 version, I received the same error once again. Here is a partial trace:
The reverse was also true. When I logged into the 3.1 version and then shut down that server and launched the 3.0.9 version, I received the same error. Here is a partial trace:
What’s notable to me is that you needn’t literally be in the process of upgrading. To reproduce this issue, you need only be running two apps spanning these two versions of Rails that are setting cookies with the same names…presumably either in sequence (as in my experiment) or concurrently (which I haven’t tried).
Hopefully, someone else here will provide a better-informed answer than this to add the details this loose explanation lacks. In the meantime, if you’re running into this issue in development and you don’t care about the inner workings, just clear your cookies (as suggested by @tscolari in the thread referenced above: https://github.com/rails/rails/issues/2509) and move along. Cheers.