# Re: anyone familiar with this BOOST error **URL:** \ **Category:** GNU Radio\ **Created:** [January 19, 2015, 6:12pm UTC](https://www.ruby-forum.com/t/re-anyone-familiar-with-this-boost-error/233879 "2015-01-19T18:12:28Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\ **Post date:** [January 19, 2015, 6:12pm UTC](https://www.ruby-forum.com/t/re-anyone-familiar-with-this-boost-error/233879/1 "2015-01-19T18:12:28Z")
I think I have a hunch as to what this is. Some googling showed that this happens when you are trying to spawn more threads than your machine can handle. From your previous post/discussions I understand this happens when you run the cdma\_rx file. The part of this program that generates a lot of threads is the aqcuisition filterbank which we have made highly parallelized. If this is the case then it should also happen running cdma\_txrx (please try it). Recall that gr-cdma is fully parameterized by the user. So to fix this (this is not a bug, it is the feature of the system) try to change the variable n\_filt=51 to some smaller value (try 11). I hope you understand what the tradeoffs are (reduced capability of receiver to handle frequency errors). best, Achilleas ---
**Author:** ![Achilleas\_A](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/74df32/32.png) [@Achilleas\_A](https://www.ruby-forum.com/u/Achilleas_A)\ **Post date:** [January 19, 2015, 6:49pm UTC](https://www.ruby-forum.com/t/re-anyone-familiar-with-this-boost-error/233879/2 "2015-01-19T18:49:23Z")
I was doing some research and saw the same similair information. Some sites were saying you can increase the processing identifier limits but I dont think I will try those. Yes the same error occurs when running the cdma\_txrx. I will try reducing the number of filters to a smaller value, and yes I understand there will be tradeoffs in doing this. I am using a laptop by the way so it probably cannot handle as many threads because of its memory, RAM, processor size etc. ``` On Monday, January 19, 2015 12:11 PM, Achilleas A. ``` [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: I think I have a hunch as to what this is. Some googling showed that this happens when you are trying to spawn more threads than your machine can handle. From your previous post/discussions I understand this happens when you run the cdma\_rx file. The part of this program that generates a lot of threads is the aqcuisition filterbank which we have made highly parallelized. If this is the case then it should also happen running cdma\_txrx (please try it). Recall that gr-cdma is fully parameterized by the user. So to fix this (this is not a bug, it is the feature of the system) try to change the variable n\_filt=51 to some smaller value (try 11). I hope you understand what the tradeoffs are (reduced capability of receiver to handle frequency errors). best, Achilleas ---
**Author:** ![Achilleas\_A](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/74df32/32.png) [@Achilleas\_A](https://www.ruby-forum.com/u/Achilleas_A)\ **Post date:** [January 19, 2015, 8:33pm UTC](https://www.ruby-forum.com/t/re-anyone-familiar-with-this-boost-error/233879/3 "2015-01-19T20:33:56Z")
Hello, I saw there has been a recent update to the master gr-cdma. Should I be doing a git pull request for the new updates as well? ``` On Monday, January 19, 2015 12:11 PM, Achilleas A. ``` [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: I think I have a hunch as to what this is. Some googling showed that this happens when you are trying to spawn more threads than your machine can handle. From your previous post/discussions I understand this happens when you run the cdma\_rx file. The part of this program that generates a lot of threads is the aqcuisition filterbank which we have made highly parallelized. If this is the case then it should also happen running cdma\_txrx (please try it). Recall that gr-cdma is fully parameterized by the user. So to fix this (this is not a bug, it is the feature of the system) try to change the variable n\_filt=51 to some smaller value (try 11). I hope you understand what the tradeoffs are (reduced capability of receiver to handle frequency errors). best, Achilleas