Make DedupeIntegration more memory efficient.

[antonpirker]

Users reported that the DedupeIntegration can use up a lot of memory, because it keeps a full exception in memory for checking if it has seen this exception already.

Depending on the users code those exception objects can be big because they also include the traceback and local variables (which can be huge).

Idea is now to not save the whole exception but just a hash of the important parts of the exception to decide if we have seen this exception again.

fixes #3165
fixes #4327

[codecov]

❌ 33 Tests Failed:

Tests completed	Failed	Passed	Skipped
24121	33	24088	5796

View the top 3 failed test(s) by shortest run time

tests.test_basics::test_option_before_breadcrumb

Stack Traces | 0.067s run time

tests/test_basics.py:240: in test_option_before_breadcrumb
    assert not reports
E   AssertionError: assert not [('event_processor', 'error')]

tests.test_basics::test_option_before_breadcrumb

Stack Traces | 0.071s run time

tests/test_basics.py:240: in test_option_before_breadcrumb
    assert not reports
E   AssertionError: assert not [('event_processor', 'error')]

tests.test_basics::test_breadcrumbs

Stack Traces | 0.072s run time

tests/test_basics.py:396: in test_breadcrumbs
    (event,) = events
E   ValueError: not enough values to unpack (expected 1, got 0)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[sl0thentr0py]

@antonpirker can't you just id(exc)?

[antonpirker]

i thought about that too. but garbage collection moves objects around. so id(exc) could be different when we safe it and when we compare it...

[antonpirker]

The id() of an object is guaranteed to never change during the life cycle of the object. So taking it.