[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [aspectj-users] In rare circumstances StackOverflows occur after aspecting Android projects
|
Hi Andreas.
It would be helpful if you could post some more info like aspect source code, weaving, application and error logs. My assumption for now is that you have more than one advice intercepting the same pointcut and at least two of them interfering with each other in an unhealty way. Depending on the way you set up and execute the timer that might also be the culprit, maybe something like calling proceed() multiple times (which is not necessarily a problem, but under certain circumstances might be).
--
Alexander Kriegisch
https://scrum-master.de
Andreas Marschke schrieb am 05.07.2016 16:25:
Hi Alexander,
when the Aspect is called we are setting up a timer for the request, that's the interesting thing we do.
We are not allowed to get source of the customer application as there are legal issues in our way blocking direct access.
The internal bookkeeping tracks the URLConnection object for later retrieval so we can stop the timer set when the URLConnection is initiated.
We only provide an SDK to our customers and a Gradle plugin automating the aspect weaving. As far as we know no other code in their application or
dependency uses AspectJ. That is, we have received a list of dependencies the project requires both for building the project as well as for running it.
None of these requirements elude to AspectJ usage inside their project outside our integration.
We are monitoring network requests, and time user interactions based off of custom timers the developer may define. This is part of our Digital Performance Management offering.
Thanks,
Andreas Marschke.